{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-11T20:40:40.676Z",
  "record_id": "VXI-EXT-ADVISORY-JSONWEBTOKEN-23540-01-v1",
  "record_kind": "external_reference",
  "title": "jsonwebtoken: Check missing-key and algorithm defaults together",
  "system": "jsonwebtoken",
  "evidence_family": "reviewed_advisory_applicability",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can a missing JWT verification key change how an unsigned token is handled?",
  "near_questions": [
    "How should an agent review missing JWT key handling?",
    "Does a missing verification secret always imply token bypass?",
    "Which conditions combine in CVE-2022-23540?",
    "Why does an omitted JWT algorithm list matter?",
    "Can an unsigned token reach a verifier with no usable key?",
    "What did jsonwebtoken 9.0.0 change for the none default?",
    "Should key-loading failures be checked with algorithm defaults?",
    "Does a package match prove all bypass conditions hold?",
    "Can one JWT setting establish application authentication safety?",
    "What evidence belongs with an unsigned-token advisory?",
    "Does this review cover every jsonwebtoken major-version change?",
    "Can an agent verify authentication from a dependency version alone?"
  ],
  "supported_claims": [
    {
      "claim": "The jsonwebtoken advisory for CVE-2022-23540 identifies three combined conditions in versions through 8.5.1: an unsigned token, no specified algorithms and a falsy verification key or secret. Under those conditions, verification can default to the none algorithm. The maintainer lists 9.0.0 as removing that default. Review missing-key handling and algorithm selection together rather than assuming one matching condition proves bypass. This is a historical library behaviour review, not verification of an application's authentication or of every issue fixed in a major upgrade.",
      "reliance": "EXTERNAL_ADVISORY_REVIEW_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "one matching condition promoted to a confirmed bypass",
    "an application authentication test claimed from documentation",
    "all upgrade behaviour or current library safety established"
  ],
  "public_summary": "The jsonwebtoken advisory for CVE-2022-23540 identifies three combined conditions in versions through 8.5.1: an unsigned token, no specified algorithms and a falsy verification key or secret. Under those conditions, verification can default to the none algorithm. The maintainer lists 9.0.0 as removing that default. Review missing-key handling and algorithm selection together rather than assuming one matching condition proves bypass. This is a historical library behaviour review, not verification of an application's authentication or of every issue fixed in a major upgrade.",
  "related_record_ids": [
    "VXI-EXT-ADVISORY-NEXT-29927-01-v1",
    "VXI-EXT-ADVISORY-PYJWT-29217-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_advisory_review",
    "source_title": "jsonwebtoken maintainer advisory: CVE-2022-23540",
    "source_url": "https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-qwph-4952-7xr6",
    "checked_on": "2026-10-11",
    "candidate_record_id": "VXI-EXT-ADVISORY-JSONWEBTOKEN-23540-01-v1",
    "candidate_record_sha256": "1ab878e537c09ddc5ee56861fbfe3b26e0697aa8ba32ba32a291f379b3af56e1",
    "method": "Primary advisory reviewed alongside hash-verified frozen source projections. Source assertions and discrepancies remain attributed; no deployment was assessed.",
    "deployment_tested_by_varexis": false,
    "frozen_advisory_sources": [
      {
        "dataset_id": "osv-20261008-s2-d17eb238c528",
        "record_id": "VXI-OSV-d394ed134654e4519324455d6a76dd310db88012-bb7382095564",
        "advisory_id": "GHSA-qwph-4952-7xr6",
        "package": "jsonwebtoken",
        "ecosystem": "npm",
        "captured_on": "2026-10-08",
        "source_pointer": "/affected/0",
        "content_sha256": "afb9df9c28773f5cdb0ef009f0900492ae0ad0f7f3f51a54c017aba5393451d3",
        "preview_url": "/api/index/advisories?record_id=VXI-OSV-d394ed134654e4519324455d6a76dd310db88012-bb7382095564"
      }
    ],
    "binding_scope": "This snapshot retains the reviewed answer and frozen source identifiers/hashes. Complete affected-package projections are separately retrievable; no deployment assessment is included.",
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research.",
    "current_lookup": {
      "dataset_id": "osv-canonical-20261013-v1",
      "checked_on": "2026-10-13",
      "withheld_source_record_ids": [],
      "boundary": "Historical catalogue reviews retain the source hashes checked when authored. A current preview, where available, is a separately versioned projection. Withheld bindings are not current retrieval or purchase targets."
    }
  },
  "answer_policy": {
    "classification": "ADVISORY_SOURCE_WITH_APPLICABILITY_BOUNDARIES",
    "bounded_answer": "The jsonwebtoken advisory for CVE-2022-23540 identifies three combined conditions in versions through 8.5.1: an unsigned token, no specified algorithms and a falsy verification key or secret. Under those conditions, verification can default to the none algorithm. The maintainer lists 9.0.0 as removing that default. Review missing-key handling and algorithm selection together rather than assuming one matching condition proves bypass. This is a historical library behaviour review, not verification of an application's authentication or of every issue fixed in a major upgrade.",
    "required_buyer_context": "Installed jsonwebtoken version, handling of unsigned tokens, algorithm options and actual key-loading failure behaviour. No authentication attempt was made.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#jsonwebtoken-missing-key-verification-conditions",
  "machine_readable_record": "/varexis-index/records/jsonwebtoken-missing-key-verification-conditions.json"
}
