CVE-2026-110513

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-11-18. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory

Also known asEUVD-2026-128519 (ENISA EUVD) · GHSA-95hx-569q-f3rv (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

Insufficient Session Expiration vulnerability in the Apache Iggy server HTTP transport. A self-issued JSON Web Token (JWT) identified the user only by numeric user ID, and a new user takes the lowest free ID. After an administrator deleted a user, that user's unexpired token, or a token refreshed from it while the ID was free, authenticated as the next account created with that ID and had that account's permissions. Only deployments with HTTP enabled are affected.

This issue affects Apache Iggy: through 0.9.0.

Users are recommended to upgrade to version 0.10.0, which fixes the issue.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
45th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 18, 2026

Last Modified

November 20, 2026

Advisory Details (3)

Auto-updated Nov 19, 2026
Fix named in the CVE record. Sources: github_pr.
Web page

oss-security - CVE-2026-110513: Apache Iggy: Deleted user's HTTP token authenticates as the account that reuses its user ID

http://www.openwall.com/lists/oss-security/2026/11/17/29
GitHub pull request

fix(server)!: bind grants and HTTP tokens to the objects they name

Fix merged in apache/iggy PR #4550 on 2026-10-16 — awaiting tagged release

https://github.com/apache/iggy/pull/4550

Vendor Advisories for CVE-2026-110513(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 12× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-22 12:46 UTCEchelonGraph re-scored
  2. 2026-11-22 12:46 UTCGHSA enrichmentGHSA-95hx-569q-f3rv · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  4. 2026-11-21 15:06 UTCGHSA enrichmentGHSA-95hx-569q-f3rv · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-11-20 17:28 UTCEchelonGraph re-scored
  6. 2026-11-20 17:28 UTCGHSA enrichmentGHSA-95hx-569q-f3rv · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.6% · 52nd percentile
  8. 2026-11-19 20:26 UTCOSV refresh
  9. 2026-11-19 20:19 UTCEchelonGraph re-scoredFirst assessed: 9.8 CRITICAL
  10. 2026-11-19 20:19 UTCGHSA enrichmentGHSA-95hx-569q-f3rv
  11. 2026-11-19 20:17 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  12. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  13. 2026-11-18 12:50 UTCGHSA enrichmentGHSA-95hx-569q-f3rv
  14. 2026-11-18 11:03 UTCENISA EUVD ID recordedEUVD-2026-128519 · Source: ENISA EUVD
  15. 2026-11-18 10:04 UTCEchelonGraph re-scored
  16. 2026-11-18 10:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-110513?
CVE-2026-110513 is a critical-severity vulnerability; its CVE record was published on November 18, 2026. Insufficient Session Expiration vulnerability in the Apache Iggy server HTTP transport. A self-issued JSON Web Token (JWT) identified the user only by numeric user ID, and a new user takes the lowest free ID. After an administrator deleted a user, that user's unexpired token, or a token refreshed…
When was the CVE record for CVE-2026-110513 published?
The CVE record for CVE-2026-110513 was published on November 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 20, 2026; the record at its source may have been updated since.
Is CVE-2026-110513 actively exploited?
CVE-2026-110513 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-110513?
CVE-2026-110513 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-110513?
The CVE record for CVE-2026-110513 names the fix: "Users are recommended to upgrade to version 0.10.0, which fixes the issue." The vendor advisories EchelonGraph has for CVE-2026-110513 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-110513?

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