Skip to content
Fencer Intel
low —

CVE-2026-132079 json

Apache Iggy Go SDK: Go TCP client creates personal access tokens that outlive the requested expiry

published 15h ago modified 9h ago also EUVD-2026-128610

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

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.

Patch / fix

  • Apache Software Foundation Apache Iggy Go SDK 0.10.0

Is CVE-2026-132079 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected products

  • Apache Software Foundation Apache Iggy Go SDK

Classification

Weakness
  • CWE-613 DEPRECATED: Insufficient Session Expiration

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.