RevocationEndpoint · Oauthlib : Unsafe JSONP callback injection
Affects confluence-markdown-exporterSource GCVE Database
Not known to be exploited · CVSS 6.1 Medium : upgrade to 5.5.0 when convenient.
Data as of 4 Nov 2026, 08:16 UTC
- Patch
- Available – fixed in 5.5.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade confluence-markdown-exporter to 5.5.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewconfluence-markdown-exporterpkg:brew/confluence-markdown-exporterOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in oauthlib version 5.5.0. Users should upgrade to version 5.5.0 or later to mitigate this vulnerability. If upgrading is not immediately possible, avoid enabling the enable_jsonp option in the RevocationEndpoint constructor. Additionally, ensure that any use of JSONP callbacks validates the callback parameter against a strict whitelist of allowed JavaScript function names to prevent injection. Since the vulnerability only affects deployments that explicitly enable JSONP, disabling this feature is an effective mitigation.
Description
Oauthlib's RevocationEndpoint has a vulnerability when JSONP support is enabled via enable_jsonp=True. The endpoint reflects the user-supplied callback parameter directly into JavaScript responses without validating it as a safe JSONP callback name. This allows an attacker who can influence the callback parameter to inject arbitrary JavaScript code into the response, which executes in the context of the client application's origin. This affects deployments that explicitly enable JSONP support for token revocation, commonly used for older browsers or cross-origin JavaScript clients.
References
- github.com/oauthlib/oauthlib/security/advisories/GHSA-hj66-6f7g-4r5v (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-49264 (opens in a new tab)
- github.com/oauthlib/oauthlib/pull/951 (opens in a new tab)
- github.com/oauthlib/oauthlib/commit/c888359f3c42bec235b2c5caab2069c9ed62457c (opens in a new tab)
- github.com/oauthlib/oauthlib (opens in a new tab)
- github.com/pypa/advisory-database/tree/main/vulns/oauthlib/PYSEC-2026-4113.yaml (opens in a new tab)