CVE-2015-10004 is a high-severity (CVSS 7.5) CWE-668 vulnerability in github.com/robbert229/jwt. A fix is available for github.com/robbert229/jwt — see the affected versions and patch details below.
robbert229/jwt's token validation methods vulnerable to a timing side-channel during HMAC comparison
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2015-10004.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/robbert229/jwtReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Token validation methods are susceptible to a timing side-channel during HMAC comparison. With a large enough number of requests over a low latency connection, an attacker may use this to determine the expected HMAC.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/robbert229/jwt | all versions | 0.0.0-20170426191122-ca1404ee6e83go get github.com/robbert229/jwt@v0.0.0-20170426191122-ca1404ee6e83 |
Affected Products
json web tokenjson_web_token_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/robbert229/jwt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/robbert229/jwt to 0.0.0-20170426191122-ca1404ee6e83 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-10004 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2015-10004 in your dependencies?
Find it across Go, including transitive dependencies.