{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-11T20:40:40.676Z",
  "record_id": "VXI-EXT-ADVISORY-PYJWT-29217-01-v1",
  "record_kind": "external_reference",
  "title": "PyJWT: Bind accepted algorithms to the intended key type",
  "system": "PyJWT",
  "evidence_family": "reviewed_advisory_applicability",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Is enabling every supported JWT algorithm safe for an agent's token-verification helper?",
  "near_questions": [
    "How should an agent review JWT algorithm and key type policy?",
    "Should a token-verification helper enable every algorithm?",
    "Can a wrapper broaden accepted JWT algorithms?",
    "Why must accepted algorithms match the intended key type?",
    "Does successful token decoding prove signature policy is correct?",
    "What does the PyJWT key-confusion advisory describe?",
    "Which historical PyJWT fix addresses this issue?",
    "Does PyJWT 2.4.0 validate application authorization?",
    "Should algorithm defaults be checked inside helper functions?",
    "Can a public verification key be treated as a shared secret?",
    "What configuration evidence belongs with a JWT advisory?",
    "Can a package update replace review of token verification policy?"
  ],
  "supported_claims": [
    {
      "claim": "PyJWT's CVE-2022-29217 advisory describes confusion between asymmetric public keys and symmetric verification when incompatible algorithms are accepted. It recommends explicitly selecting the expected algorithms. The frozen source covers versions from 1.5.0 before 2.4.0; the maintainer lists 2.4.0 as patched. For a verification helper, review the accepted algorithm set and intended key type together, including defaults introduced by wrappers. A token decoding successfully is not evidence of correct signature policy or application authorization. The historical patch does not validate a buyer's configuration.",
      "reliance": "EXTERNAL_ADVISORY_REVIEW_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "successful decoding treated as verified authorization",
    "a wrapper's algorithm policy inferred from package version",
    "historical patch treated as buyer-configuration validation"
  ],
  "public_summary": "PyJWT's CVE-2022-29217 advisory describes confusion between asymmetric public keys and symmetric verification when incompatible algorithms are accepted. It recommends explicitly selecting the expected algorithms. The frozen source covers versions from 1.5.0 before 2.4.0; the maintainer lists 2.4.0 as patched. For a verification helper, review the accepted algorithm set and intended key type together, including defaults introduced by wrappers. A token decoding successfully is not evidence of correct signature policy or application authorization. The historical patch does not validate a buyer's configuration.",
  "related_record_ids": [
    "VXI-EXT-ADVISORY-NEXT-29927-01-v1",
    "VXI-EXT-ADVISORY-JSONWEBTOKEN-23540-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_advisory_review",
    "source_title": "PyJWT maintainer advisory: CVE-2022-29217",
    "source_url": "https://github.com/jpadilla/pyjwt/security/advisories/GHSA-ffqj-6fqr-9h24",
    "checked_on": "2026-10-11",
    "candidate_record_id": "VXI-EXT-ADVISORY-PYJWT-29217-01-v1",
    "candidate_record_sha256": "18590059f78cf6a0216a52f4f313d3d4e1d34be21a94d2f40c00c834f3b999d6",
    "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-017562cdfb326a1688502139f4ca18798c189fa9-2ace5abe1730",
        "advisory_id": "GHSA-ffqj-6fqr-9h24",
        "package": "pyjwt",
        "ecosystem": "PyPI",
        "captured_on": "2026-10-08",
        "source_pointer": "/affected/0",
        "content_sha256": "21d87e792293e4b71e679137e1ef883cc3328601fdc1900a070142623498c80d",
        "preview_url": "/api/index/advisories?record_id=VXI-OSV-017562cdfb326a1688502139f4ca18798c189fa9-2ace5abe1730"
      }
    ],
    "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": "PyJWT's CVE-2022-29217 advisory describes confusion between asymmetric public keys and symmetric verification when incompatible algorithms are accepted. It recommends explicitly selecting the expected algorithms. The frozen source covers versions from 1.5.0 before 2.4.0; the maintainer lists 2.4.0 as patched. For a verification helper, review the accepted algorithm set and intended key type together, including defaults introduced by wrappers. A token decoding successfully is not evidence of correct signature policy or application authorization. The historical patch does not validate a buyer's configuration.",
    "required_buyer_context": "Resolved PyJWT version, accepted algorithms, key type and wrapper behaviour at the verification call. No tokens or customer keys were examined.",
    "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#pyjwt-algorithm-and-key-type-policy",
  "machine_readable_record": "/varexis-index/records/pyjwt-algorithm-and-key-type-policy.json"
}
