# CVE-2026-132079: Apache Iggy Go SDK: Go TCP client creates personal access tokens that outlive the requested expiry


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-348j-xx47-r332

## What is CVE-2026-132079?

CVE-2026-132079 is a critical vulnerability in Apache Iggy Go SDK, published on 18 Nov 2026. 

### Official 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.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2026-132079?

1 open source package ship an affected version, including github.com/apache/iggy/foreign/go.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `github.com/apache/iggy/foreign/go` | Go | `pkg:golang/github.com/apache/iggy/foreign/go` | From 0.5.0 | 0.10.0 |

## How do I fix CVE-2026-132079?

Upgrade each affected package to the fixed version listed for it above. Each package has its own fixed versions.

## Is CVE-2026-132079 being exploited?

There is no known exploitation of CVE-2026-132079 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-132079 and fix it if it is affected.

What it is: CVE-2026-132079 is a critical vulnerability in Apache Iggy Go SDK, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-132079 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/apache/iggy/foreign/go (Go): affected from 0.5.0; fixed in 0.10.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-132079/ (Markdown: https://insights.sbomify.com/CVE-2026-132079/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-132079
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-132079
- OSV: https://osv.dev/vulnerability/CVE-2026-132079

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-132079/
Summaries are generated and may contain mistakes; the official description above is the record.
