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.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 18 Nov 2026 12:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Apache Iggy Go SDK: Go TCP client creates personal access tokens that outlive the requested expiry | |
| Weaknesses | CWE-613 | |
| References |
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2026-11-18T11:57:51.156Z
Reserved: 2026-11-18T11:05:37.365Z
Link: CVE-2026-132079
No data.
Status : Received
Published: 2026-11-18T12:17:22.700
Modified: 2026-11-18T12:17:22.700
Link: CVE-2026-132079
No data.
OpenCVE Enrichment
No data.
-
CWE-613
Insufficient Session Expiration