Loading vulnerability…
CVE-2026-49265 is a timing side-channel vulnerability in OAuthLib's PKCE authorization-code verifier comparison. The plain PKCE comparison uses Python string equality instead of a constant-time comparison, potentially exposing a timing oracle. An attacker who intercepts an authorization code and can perform repeated, precisely timed token requests may infer the code verifier character by character and redeem the code. Exploitation could lead to access-token theft and account takeover, but is constrained by authorization-code single-use semantics and network jitter.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability affecting oauthlib, addressed in version 4.0.0 or later. The advisory assigns a CVSS v3 score of 6.8, indicating network exploitation with high attack complexity, no required privileges, and required user interaction. Potential impacts are high confidentiality and integrity loss, with no availability impact. The underlying flaw is not described.
CWE-208 observable timing-discrepancy vulnerability in oauthlib's PKCE authorization-code grant validation. Non-constant-time comparison of attacker-supplied code verifiers can expose a timing oracle that may enable character-by-character recovery of a verifier under controlled conditions. It affects oauthlib versions 3.0.0 through versions before 4.0.0.
A medium-severity vulnerability (CWE-208) affecting oauthlib and related packages prior to version 4.0.0. The provided CVSS v3 score is 6.8; exploitation requires user interaction and has high confidentiality and integrity impact.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.