{"items":[{"id":"NVI-00013139","kind":"vulnerability","title":"PyJWT: ReDoS vulnerability when calling the `is_pem_format` function.","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-jwrc-g2q2-pq5p","CVE-2026-102270"],"plain_summary":"GitHub lists this reviewed advisory for pyjwt. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-06182f339258a68ea4b594a26aaf09a3"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-30T14:40:26.000Z","value":"4.4 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-716e929f52774f4e7b1b50f78d82a987"},{"kind":"CVSS","as_of":"2026-10-06T18:46:19.343Z","value":"4.4 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-17dc26a1be6a1d29185fd9089a314b0f"},{"kind":"CVSS","as_of":"2026-10-06T18:46:19.343Z","value":"4.9 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-17dc26a1be6a1d29185fd9089a314b0f"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.246%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.15886. Missing scores are unknown.","source_id":"sr-06182f339258a68ea4b594a26aaf09a3"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-716e929f52774f4e7b1b50f78d82a987","url":"https://github.com/advisories/GHSA-jwrc-g2q2-pq5p","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jwrc-g2q2-pq5p","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T07:24:25.558Z"},{"id":"sr-17dc26a1be6a1d29185fd9089a314b0f","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-102270","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-102270","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:04.487Z"},{"id":"sr-06182f339258a68ea4b594a26aaf09a3","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-102270","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:44:07.769Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-716e929f52774f4e7b1b50f78d82a987"],"technology":"pyjwt","known_exclusions":[],"conditions_summary":"### Summary\nThere is a Re-DoS vulnerability in the `is_pem_format` function which results in a intesive CPU usage if an attacker is been able to provide a custom certificate.\n\n\n### Details\nThe problem is that the lazy quantifier `.+?` will always first try to match as little as possible until it finds a `---- END`. Normally this means the complexity of this should be O(N). However, by providing an input which consists only of `----BEGIN CERTIFICATE-----` lines and no `---- END` line, the regex algorithm will first try to match the first line and then, with the lazy quantifier, all the lines until the end O(N), which then fails since it is unable to find a `---- END` line. It will then jump to the next line, resulting in N re-scans of the whole string, which means the complexity basically results in O(N²). \n\n\n### PoC\n```python\nimport time\nimport re\n\n\nBEGIN_LINE = b\"-----BEGIN CERTIFICATE-----\\n\"\n\n_PEMS = {\n    b\"CERTIFICATE\",\n    b\"TRUSTED CERTIFICATE\",\n    b\"PRIVATE KEY\",\n    b\"PUBLIC KEY\",\n    b\"ENCRYPTED PRIVATE KEY\",\n    b\"OPENSSH PRIVATE KEY\",\n    b\"DSA PRIVATE KEY\",\n    b\"RSA PRIVATE KEY\",\n    b\"RSA PUBLIC KEY\",\n    b\"EC PRIVATE KEY\",\n    b\"DH PARAMETERS\",\n    b\"NEW CERTIFICAT","public_affected_ranges":["<= 2.13.0"]}],"null_published_at":"2026-11-04T10:04:41.549Z","source_updated_at":"2026-09-30T14:40:26.000Z","source_disclosed_at":"2026-09-30T14:40:25.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-01T07:24:25.558Z"},{"id":"NVI-00013139","kind":"vulnerability","title":"PyJWT: ReDoS vulnerability when calling the `is_pem_format` function.","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-jwrc-g2q2-pq5p","CVE-2026-102270"],"plain_summary":"GitHub lists this reviewed advisory for pyjwt. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-17dc26a1be6a1d29185fd9089a314b0f"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-30T14:40:26.000Z","value":"4.4 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-716e929f52774f4e7b1b50f78d82a987"},{"kind":"CVSS","as_of":"2026-10-06T18:46:19.343Z","value":"4.4 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-17dc26a1be6a1d29185fd9089a314b0f"},{"kind":"CVSS","as_of":"2026-10-06T18:46:19.343Z","value":"4.9 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-17dc26a1be6a1d29185fd9089a314b0f"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-716e929f52774f4e7b1b50f78d82a987","url":"https://github.com/advisories/GHSA-jwrc-g2q2-pq5p","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jwrc-g2q2-pq5p","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T07:24:25.558Z"},{"id":"sr-17dc26a1be6a1d29185fd9089a314b0f","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-102270","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-102270","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:04.487Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-716e929f52774f4e7b1b50f78d82a987"],"technology":"pyjwt","known_exclusions":[],"conditions_summary":"### Summary\nThere is a Re-DoS vulnerability in the `is_pem_format` function which results in a intesive CPU usage if an attacker is been able to provide a custom certificate.\n\n\n### Details\nThe problem is that the lazy quantifier `.+?` will always first try to match as little as possible until it finds a `---- END`. Normally this means the complexity of this should be O(N). However, by providing an input which consists only of `----BEGIN CERTIFICATE-----` lines and no `---- END` line, the regex algorithm will first try to match the first line and then, with the lazy quantifier, all the lines until the end O(N), which then fails since it is unable to find a `---- END` line. It will then jump to the next line, resulting in N re-scans of the whole string, which means the complexity basically results in O(N²). \n\n\n### PoC\n```python\nimport time\nimport re\n\n\nBEGIN_LINE = b\"-----BEGIN CERTIFICATE-----\\n\"\n\n_PEMS = {\n    b\"CERTIFICATE\",\n    b\"TRUSTED CERTIFICATE\",\n    b\"PRIVATE KEY\",\n    b\"PUBLIC KEY\",\n    b\"ENCRYPTED PRIVATE KEY\",\n    b\"OPENSSH PRIVATE KEY\",\n    b\"DSA PRIVATE KEY\",\n    b\"RSA PRIVATE KEY\",\n    b\"RSA PUBLIC KEY\",\n    b\"EC PRIVATE KEY\",\n    b\"DH PARAMETERS\",\n    b\"NEW CERTIFICAT","public_affected_ranges":["<= 2.13.0"]}],"null_published_at":"2026-11-03T10:03:31.373Z","source_updated_at":"2026-09-30T14:40:26.000Z","source_disclosed_at":"2026-09-30T14:40:25.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-11-01T07:24:25.558Z"},{"id":"NVI-00013139","kind":"vulnerability","title":"PyJWT: ReDoS vulnerability when calling the `is_pem_format` function.","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jwrc-g2q2-pq5p","CVE-2026-102270"],"plain_summary":"GitHub lists this reviewed advisory for pyjwt. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-716e929f52774f4e7b1b50f78d82a987"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-30T14:40:26.000Z","value":"4.4 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-716e929f52774f4e7b1b50f78d82a987"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-716e929f52774f4e7b1b50f78d82a987","url":"https://github.com/advisories/GHSA-jwrc-g2q2-pq5p","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jwrc-g2q2-pq5p","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T07:24:25.558Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-716e929f52774f4e7b1b50f78d82a987"],"technology":"pyjwt","known_exclusions":[],"conditions_summary":"### Summary\nThere is a Re-DoS vulnerability in the `is_pem_format` function which results in a intesive CPU usage if an attacker is been able to provide a custom certificate.\n\n\n### Details\nThe problem is that the lazy quantifier `.+?` will always first try to match as little as possible until it finds a `---- END`. Normally this means the complexity of this should be O(N). However, by providing an input which consists only of `----BEGIN CERTIFICATE-----` lines and no `---- END` line, the regex algorithm will first try to match the first line and then, with the lazy quantifier, all the lines until the end O(N), which then fails since it is unable to find a `---- END` line. It will then jump to the next line, resulting in N re-scans of the whole string, which means the complexity basically results in O(N²). \n\n\n### PoC\n```python\nimport time\nimport re\n\n\nBEGIN_LINE = b\"-----BEGIN CERTIFICATE-----\\n\"\n\n_PEMS = {\n    b\"CERTIFICATE\",\n    b\"TRUSTED CERTIFICATE\",\n    b\"PRIVATE KEY\",\n    b\"PUBLIC KEY\",\n    b\"ENCRYPTED PRIVATE KEY\",\n    b\"OPENSSH PRIVATE KEY\",\n    b\"DSA PRIVATE KEY\",\n    b\"RSA PRIVATE KEY\",\n    b\"RSA PUBLIC KEY\",\n    b\"EC PRIVATE KEY\",\n    b\"DH PARAMETERS\",\n    b\"NEW CERTIFICAT","public_affected_ranges":["<= 2.13.0"]}],"null_published_at":"2026-11-01T07:29:12.925Z","source_updated_at":"2026-09-30T14:40:26.000Z","source_disclosed_at":"2026-09-30T14:40:25.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-01T07:24:25.558Z"}],"next_cursor":null,"snapshot_revision":"42594"}