Apache Iggy Server HTTP Transport Insufficient Session Expiration Vulnerability
Is it fixed? Not yet.
Ongoing since Nov 18, 10:16 UTC. First reported Nov 18, 10:16 UTC.
What happened
An insufficient session expiration vulnerability exists in the Apache Iggy server HTTP transport where deleted user IDs can be reassigned, allowing unexpired or refreshed JWTs to authenticate as the newly created account with that ID. Only deployments with HTTP enabled are affected.
What caused it?
A self-issued JSON Web Token (JWT) identified the user only by numeric user ID, and a new user takes the lowest free ID, allowing an unexpired token from a deleted user to authenticate as the next account created with that ID.
Source: tenable.com
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Timeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on security advisory
Apache Iggy server HTTP transport.: CVE-2026-110513 (Critical)
Source
Evidence
1 report · 1 CVEShow
- [1]CVE First reportApache Iggy server HTTP transport.: CVE-2026-110513 (Critical)(opens security advisory in a new tab)
Critical severity. 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…
by Tenable 0upvotes 0comments
FAQ
What happened in the Apache issue?
An insufficient session expiration vulnerability exists in the Apache Iggy server HTTP transport where deleted user IDs can be reassigned, allowing unexpired or refreshed JWTs to authenticate as the newly created account with that ID. Only deployments with HTTP enabled are affected.
What is affected by the Apache issue?
Apache.
When did the Apache issue start and end?
It started Nov 18, 10:16 UTC and is still ongoing (18 h 27 min so far). This page updates as it develops.
How do I get alerts for Apache?
Subscribe to the Apache RSS feed for every new Apache incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Apache is down. Apache feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.