Apache Iggy Go SDK Fix Requires Replacing Overlong Access Tokens
Quick Answer
Update the Iggy Go SDK to 0.10.0 and replace access tokens created through affected TCP clients; upgrading alone does not repair existing expiry values.
Confirm Scope And Apply The Supported Remediation
What to do now: Identify services and tools using Iggy Go SDK 0.5.0–0.9.x to create tokens through TCP. Record token owners, creation paths and intended expiry policy without exporting secrets. Match the Go TCP CreatePersonalAccessToken path. The announcement does not establish the same encoding defect in other SDKs or transports. Upgrade and redeploy the SDK consumers, delete affected tokens on the server and create replacements with the corrected client. Coordinate credential updates with service owners. Verify actual server-side expiry against the requested lifetime and test dependent services. Retain token identifiers, revocation evidence, version records and expiry checks without storing token values.
Last verified: 2026-11-18 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Apache Iggy Go SDK TCP client |
|---|---|
| Advisory | CVE-2026-132079 |
| CVE | CVE-2026-132079 |
| Authoritative release date | 2026-11-18T11:07:35Z — timestamp of Apache’s original project announcement. |
| Authority revision date | No separate material revision is established for this release. |
| Affected versions | Apache Iggy Go SDK versions from 0.5.0 before 0.10.0 when creating personal access tokens through the TCP client. |
| Fixed version | Apache Iggy Go SDK 0.10.0; delete tokens created by the affected client and issue replacements. |
| CVSS base score | Not provided by the authority |
| CVSS severity | Low |
| Exploitation status | Apache does not confirm exploitation of this vulnerability in the cited announcement.; no exploitation claim is inferred. |
What Changed
The Go TCP client placed the requested expiry in the wrong half of the server’s 64-bit field. Nonzero lifetimes became roughly 4.3 billion times longer than requested; existing tokens retain that lifetime after the client update.
What To Validate Now
- Inventory. Identify services and tools using Iggy Go SDK 0.5.0–0.9.x to create tokens through TCP. Record token owners, creation paths and intended expiry policy without exporting secrets.
- Establish applicability. Match the Go TCP CreatePersonalAccessToken path. The announcement does not establish the same encoding defect in other SDKs or transports.
- Remediate. Upgrade and redeploy the SDK consumers, delete affected tokens on the server and create replacements with the corrected client. Coordinate credential updates with service owners.
- Validate. Verify actual server-side expiry against the requested lifetime and test dependent services. Retain token identifiers, revocation evidence, version records and expiry checks without storing token values.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Token deletion can interrupt dependent automation. Plan replacement and recovery under change control; do not leave old overlong tokens active merely because the SDK is updated.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.

