CVE-2026-132079: Apache Iggy Go SDK: Go TCP client creates personal access tokens that outlive the requested expiry
Exploitation: None known · CVSS 9.8 Critical · Unauthenticated · Published 2026-11-18
Description
Insufficient Session Expiration vulnerability in the Apache Iggy Go SDK. The TCP client method CreatePersonalAccessToken wrote the 32-bit expiry into the upper half of the 64-bit expiry field that the server reads. The server read a nonzero expiry as 2^32 times the requested value. A token created through the Go TCP client therefore stayed valid about four billion times longer than the caller asked for. This issue affects Apache Iggy Go SDK: from 0.5.0 before 0.10.0. Users are recommended to upgrade to version 0.10.0, which fixes the issue. Tokens that an earlier version created keep their long expiry on the server. Delete those tokens and create new ones.
Enclave's analysis
The Go SDK for Apache Iggy writes a personal access token's expiry into the wrong half of a 64-bit field, so any token the TCP client creates ends up valid roughly four billion times longer than requested — effectively forever. There's no direct attacker trigger; the bug only matters once such a token leaks, giving whoever finds it a far longer window to use it. No working exploit, PoC, or active exploitation has turned up anywhere, and the 9.8 CVSS score reflects worst-case impact, not ease of exploitation. Upgrade to 0.10.0 and manually revoke every token a vulnerable client ever created.
Fix
Upgrade Apache Iggy Go SDK to 0.10.0; Apache Iggy Go SDK (github.com/apache/iggy/foreign/go) to 0.10.0.
Affected versions
| Product | Vulnerable | Fixed in |
|---|---|---|
| Apache Iggy Go SDK | 0.5.0 before 0.10.0 | 0.10.0 |
| Apache Iggy Go SDK (github.com/apache/iggy/foreign/go) | >=0.5.0, <0.10.0 | 0.10.0 |