CVE-2026-88819

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% 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 — 4 sources updated this week
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In Siglet current and past versions the refresh token handler do not enforce proof of possession of the issuer DID.

CVSS v3
6.3
EG Score
6.3(medium)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

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
Severity63% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

September 14, 2026

Last Modified

September 16, 2026

Advisory Details (1)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

[Eclipse Data Plane Core] Proof-of-possession bypass in `JwtTokenManager::renew()` via attacker-chosen DID issuer (#931) · Issues · Eclipse Projects Security / vulnerability-reports · GitLab

https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/931

Vendor Advisories for CVE-2026-88819(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 21× 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-19 20:30 UTCEG score recompute
  2. 2026-09-19 20:30 UTCGHSA enrichment
  3. 2026-09-18 20:44 UTCEG score recompute
  4. 2026-09-18 20:44 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-17 20:54 UTCEG score recompute
  7. 2026-09-17 20:54 UTCGHSA enrichment
  8. 2026-09-17 19:32 UTCEPSS rescore
  9. 2026-09-16 21:08 UTCGHSA enrichment
  10. 2026-09-16 19:59 UTCEG score recompute
  11. 2026-09-16 19:59 UTCGHSA enrichment
  12. 2026-09-16 14:09 UTCEPSS rescore
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-15 20:09 UTCGHSA enrichment
  15. 2026-09-14 20:24 UTCEG score recompute
  16. 2026-09-14 20:23 UTCGHSA enrichment
  17. 2026-09-14 19:30 UTCEG score recompute
  18. 2026-09-14 19:30 UTCGHSA enrichment
  19. 2026-09-14 16:24 UTCEG score recompute
  20. 2026-09-14 15:45 UTCEG score recompute
  21. 2026-09-14 15:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-88819?
CVE-2026-88819 is a medium vulnerability published on September 14, 2026. In Siglet current and past versions the refresh token handler do not enforce proof of possession of the issuer DID.
When was CVE-2026-88819 disclosed?
CVE-2026-88819 was first published in the National Vulnerability Database on September 14, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-88819 actively exploited?
CVE-2026-88819 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.5% of all scored CVEs.
What is the CVSS score of CVE-2026-88819?
CVE-2026-88819 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-88819?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-88819, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-88819

Explore →

Is Your Infrastructure Affected by CVE-2026-88819?

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

Start Free Scan →Browse All CVEs