CVE-2026-62995

LOWPre-NVD 2.32.3—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
2.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 2.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

joserfc is a Python library that provides an implementation of several JSON Object Signing and Encryption (JOSE) standards. in versions 1.7.1 and prior, joserfc accepts JWTs with trailing padding (==) which are not conforming to the JOSE specifications. This leads to malleability of the JWTs when consumed by joserfc. Depending on this application this might or not be an issue. This could lead to bypass of token revocation or anti-replay protection when implemented as a deny list of tokens or a deny list of token hashes. Note that ECDSA JWS are always malleable because of the malleability of ECDSA signatures (first test case in the code bellow). This makes a scheme which assumes that JWTs are not malleable brittle. However for other signatures (or MAC) schemes it might make sense to assume non malleability of the token. This issue has been fixed in version 1.7.2.

CVSS v3
2.3
EG Score
2.3LOWmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity23% × 45%
Exploitation0% × 40%
Automatability100% × 15%
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

Published

July 29, 2026

Last Modified

July 30, 2026

Vendor Advisories for CVE-2026-62995(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatjaeger-main-2.20.0-0.8.hum12026-07-30redhat

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
joserfc1.1.0-1 ... 1.7.4-1 (22 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
joserfc1.1.0-1 ... 1.7.1-1 (19 versions)1.7.2-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-28 13:51 UTCEPSS rescore
  2. 2026-09-27 19:36 UTCEG score recompute
  3. 2026-09-27 19:36 UTCVendor advisory
  4. 2026-09-26 15:59 UTCEPSS rescore
  5. 2026-09-23 03:29 UTCEG score recompute
  6. 2026-09-23 03:29 UTCVendor advisory
  7. 2026-09-20 03:54 UTCEG score recompute
  8. 2026-09-20 03:54 UTCVendor advisory
  9. 2026-09-18 19:28 UTCEPSS rescore
  10. 2026-09-17 04:17 UTCEG score recompute
  11. 2026-09-17 04:17 UTCVendor advisory
  12. 2026-09-16 14:08 UTCEPSS rescore
  13. 2026-09-14 04:43 UTCEG score recompute
  14. 2026-09-14 04:43 UTCVendor advisory
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-11 09:37 UTCEPSS rescore
  17. 2026-09-11 05:09 UTCEG score recompute
  18. 2026-09-11 05:09 UTCVendor advisory
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-08 04:51 UTCEG score recompute
  21. 2026-09-08 04:51 UTCVendor advisory
  22. 2026-09-06 13:47 UTCEPSS rescore
  23. 2026-09-05 15:31 UTCEPSS rescore
  24. 2026-09-05 05:10 UTCEG score recompute
  25. 2026-09-05 05:10 UTCVendor advisory
Show 55 more
  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-01 22:46 UTCEG score recompute
  3. 2026-09-01 22:46 UTCVendor advisory
  4. 2026-09-01 13:54 UTCEPSS rescore
  5. 2026-08-30 19:17 UTCEPSS rescore
  6. 2026-08-30 01:22 UTCEPSS rescore
  7. 2026-08-29 23:12 UTCEG score recompute
  8. 2026-08-29 23:12 UTCVendor advisory
  9. 2026-08-28 21:42 UTCEPSS rescore
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-26 19:37 UTCEG score recompute
  12. 2026-08-26 19:37 UTCVendor advisory
  13. 2026-08-26 14:46 UTCEPSS rescore
  14. 2026-08-23 16:48 UTCEG score recompute
  15. 2026-08-23 16:48 UTCVendor advisory
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-21 23:49 UTCEPSS rescore
  18. 2026-08-20 22:55 UTCEPSS rescore
  19. 2026-08-20 17:14 UTCVendor advisory
  20. 2026-08-17 17:38 UTCEG score recompute
  21. 2026-08-17 17:38 UTCVendor advisory
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 18:01 UTCEG score recompute
  26. 2026-08-14 18:01 UTCVendor advisory
  27. 2026-08-13 22:00 UTCEPSS rescore
  28. 2026-08-12 13:51 UTCEPSS rescore
  29. 2026-08-11 18:28 UTCEG score recompute
  30. 2026-08-11 18:28 UTCVendor advisory
  31. 2026-08-09 13:47 UTCEPSS rescore
  32. 2026-08-08 18:54 UTCEG score recompute
  33. 2026-08-08 18:54 UTCVendor advisory
  34. 2026-08-08 16:37 UTCEPSS rescore
  35. 2026-08-06 13:47 UTCEPSS rescore
  36. 2026-08-05 19:20 UTCEG score recompute
  37. 2026-08-05 19:20 UTCVendor advisory
  38. 2026-08-05 19:17 UTCEPSS rescore
  39. 2026-08-05 19:17 UTCEPSS rescore
  40. 2026-08-04 15:10 UTCEPSS rescore
  41. 2026-08-04 10:39 UTCEPSS rescore
  42. 2026-08-03 10:36 UTCEPSS rescore
  43. 2026-08-02 19:47 UTCEG score recompute
  44. 2026-08-02 19:47 UTCVendor advisory
  45. 2026-08-01 04:16 UTCEPSS rescore
  46. 2026-07-30 20:13 UTCEG score recompute
  47. 2026-07-30 20:13 UTCVendor advisory
  48. 2026-07-30 16:28 UTCEPSS rescore
  49. 2026-07-30 15:38 UTCEG score recompute
  50. 2026-07-30 15:38 UTCVendor advisory
  51. 2026-07-30 15:00 UTCEG score recompute
  52. 2026-07-30 15:00 UTCVendor advisory
  53. 2026-07-29 19:32 UTCEG score recompute
  54. 2026-07-29 18:34 UTCEG score recompute
  55. 2026-07-29 18:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-62995?
CVE-2026-62995 is a low vulnerability published on July 29, 2026. joserfc is a Python library that provides an implementation of several JSON Object Signing and Encryption (JOSE) standards. in versions 1.7.1 and prior, joserfc accepts JWTs with trailing padding (==) which are not conforming to the JOSE specifications. This leads to malleability of the JWTs when…
When was CVE-2026-62995 disclosed?
CVE-2026-62995 was first published on July 29, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62995 actively exploited?
CVE-2026-62995 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62995?
CVE-2026-62995 has a CVSS base score of 2.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62995?
A fix for CVE-2026-62995 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62995 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-62995?

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