CVE-2026-114620

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.4 from GitHub Security Advisory (severity: MODERATE) published 2026-10-27. A secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-108522 (ENISA EUVD) · GHSA-x4rv-c3wx-4cr8 (GitHub Security Advisories)Source: ENISA EUVD

5.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.4Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.9.0, Authlib's RFC 9101 JWTAuthenticationRequest passes the unauthenticated, client-controlled request_uri parameter to the abstract get_request_object() hook before applying a destination or registration policy; the hook itself performs no network request, while the documentation demonstrates an unrestricted HTTP fetch. In deployments whose integrator implements that hook as an unrestricted outbound fetch, a remote attacker who knows a valid public client identifier can make the authorization server request internal, link-local, or otherwise unintended URLs and can distinguish fetch outcomes through different error responses and timing. Deployments whose custom hook already applies a secure allowlist, destination controls, and retrieval limits are not affected. The JWTAuthenticationRequest implementation in authlib/oauth2/rfc9101/authorization_server.py forwards request_uri to get_request_object() before an application-approved retrieval policy accepts the destination. This issue is fixed in version 1.9.0.

CVSS v3
5.4
EG Score
5.4MEDIUMhigh confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 22, 2026

Last Modified

October 30, 2026

Advisory Details (5)

Auto-updated Oct 22, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

v1.9.0

Patch available: authlib/authlib v1.9.0

https://github.com/authlib/authlib/releases/tag/v1.9.0
GitHub commit Patch Available

commit 891e3f10ae59 (authlib/authlib)

Patch available: authlib/authlib v1.9.0 (contains commit 891e3f10ae59)

https://github.com/authlib/authlib/commit/891e3f10ae5989176211f8be35dcc7cd40aa92c6
GitHub commit Patch Available

commit 6563f6f7a8c2 (authlib/authlib)

Patch available: authlib/authlib v1.9.0 (contains commit 6563f6f7a8c2)

https://github.com/authlib/authlib/commit/6563f6f7a8c2f71d2f85ee7511d72a4fbae3acc0
GitHub pull request Patch Available

fix(oauth): enforce nonce and JAR request validation

Patch available: authlib/authlib v1.9.0 (PR #949 merged 2026-10-12)

https://github.com/authlib/authlib/pull/949
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Unvalidated request_uri fetch in JWT-secured authorization request (JAR) leading to SSRF · Advisory · authlib/authlib · GitHub

https://github.com/authlib/authlib/security/advisories/GHSA-x4rv-c3wx-4cr8

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipauthlib @ 1.9.0 (fixes >= 1.6.0, < 1.9.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
authlib1.6.0 ... 1.8.0 (17 versions)
  • 1.6.0 up to 1.9.0: fixed in 1.9.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 21× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-x4rv-c3wx-4cr8 · GitHub severity MODERATE · GitHub CVSS 5.4
  3. 2026-11-01 07:59 UTCEG score recompute
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-30 21:26 UTCEG score recompute
  6. 2026-10-30 20:25 UTCEG score recompute
  7. 2026-10-30 20:19 UTCEG score recompute
  8. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-10-29 15:07 UTCEG score recompute
  11. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  13. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-10-25 14:50 UTCEG score recompute
  16. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  17. 2026-10-23 19:48 UTCEG score recompute
  18. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  19. 2026-10-22 22:29 UTCEG score recompute
  20. 2026-10-22 21:47 UTCEG score recomputeFirst assessed: 5.4 MEDIUM
  21. 2026-10-22 21:45 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-114620?
CVE-2026-114620 is a medium-severity vulnerability; its CVE record was published on October 22, 2026. Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.9.0, Authlib's RFC 9101 JWTAuthenticationRequest passes the unauthenticated, client-controlled request_uri parameter to the abstract get_request_object() hook before applying a destination or registration policy;…
When was the CVE record for CVE-2026-114620 published?
The CVE record for CVE-2026-114620 was published on October 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-114620 actively exploited?
CVE-2026-114620 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-114620?
CVE-2026-114620 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-114620?
A fix for CVE-2026-114620 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-114620

Explore →

Is Your Infrastructure Affected by CVE-2026-114620?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs