CVE-2026-132079: Apache Iggy Go SDK · DEPRECATED: Insufficient Session Expiration
Affects Apache Iggy Go SDKSource CVE Database V5
Not known to be exploited : upgrade to 0.10.0 soon.
Data as of 18 Nov 2026, 12:21 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 0.10.0
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade Apache Iggy Go SDK and github.com/apache/iggy/foreign/go to 0.10.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Iggy Go SDKgithub.com/apache/iggy/foreign/go | Affected
| Fixed in
|
Gogithub.com/apache/iggy/foreign/gopkg:golang/github.com/apache/iggy/foreign/goOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to Apache Iggy Go SDK version 0.10.0 or later, where this issue is fixed. Additionally, delete any personal access tokens created by earlier vulnerable versions and generate new tokens to ensure proper expiration enforcement.
Description
CVE-2026-132079 is an insufficient session expiration vulnerability in the Apache Iggy Go SDK versions 0.5.0 up to but not including 0.10.0. The issue arises because the CreatePersonalAccessToken method writes a 32-bit expiry value into the upper half of a 64-bit expiry field, causing the server to interpret the token's validity period as approximately four billion times longer than intended. This results in tokens remaining valid far beyond their expected expiration. The vulnerability is fixed in version 0.10.0. Users should upgrade and delete any tokens created by earlier versions to mitigate the risk.