C20/100
Vulnerability · high
Apache Iggy authorization flaws disclosed (CVE-2026-110513, CVE-2026-58320)
Tier C · Keep an eye on it – Check if you’re affected
Who’s exposed: Apache Iggy server deployments through 0.9.0 across HTTP and binary transports
Tier C because: Hits tech teams
Reach
Attack
Damage
Fix
What to do
- Upgrade Apache Iggy to a version newer than 0.9.0
The Brief
- CVE-2026-110513 (rated moderate): in Apache Iggy through 0.9.0, a deleted user's self-issued HTTP JWT authenticates as whichever account later reuses that numeric user ID.
- CVE-2026-58320 (rated important): in Apache Iggy before 0.9.0, the snapshot command (GetSnapshot on binary transports, POST /snapshot on HTTP) lacked an authorization check.
- Both issues were posted to the oss-sec mailing list on 2026-11-17 by Hubert Gruszecki.
Why it matters
Deployments of Apache Iggy at or before 0.9.0 may let stale tokens act as reused accounts or let callers take snapshots without authorization. Operators should check their version and upgrade.
The checklist behind the tier
Checklist · 1 of 10 yes
| Yes | Hits tech teams | Judgment: Apache Iggy is server software that developers and ops teams run. |
| No | Core infrastructure | Judgment: a single streaming server product, not software nearly every team runs. |
| No | Popular tool | Judgment: Apache Iggy is a niche message streaming platform, not widely used. |
| No | Exploited in the wild | Open Source Security advisories describe the flaws only; no observed attacks reported. |
| No | Public exploit | Open Source Security advisories give no exploit code or proof-of-concept. |
| No | Remote, no login | Sources do not say unauthenticated network access suffices; CVE-2026-110513 involves a self-issued token. |
| No | Full takeover | Sources do not describe code execution, root/admin rights or full account takeover. |
| No | Secrets exposed | Sources report no stolen credentials, tokens, configs or customer data. |
| No | Supply chain | Sources describe authorization bugs in the server, not compromised packages or updates. |
| No | No fix yet | Sources list affected versions through 0.9.0 and before 0.9.0 but do not state no fix exists. |
The official record
From CVE.org, CISA’s Known Exploited Vulnerabilities catalog, FIRST EPSS and the GitHub Advisory Database. Where these answer a checklist fact, they win over the reporting.
- Exploited
- Not in CISA’s exploited catalog
- Exploited
- Not in CISA’s exploited catalog
Timeline
Full coverage · 2 sources
First seen · 2 sources · Full story page · How tiers are decided