- Exploited
- No known exploitation
- Fix
- Fixed in 0.10.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.10.0.
Summary
The Apache Iggy Go SDK's TCP client method CreatePersonalAccessToken writes the token expiry incorrectly, so tokens it creates stay valid about four billion times longer than requested. Tokens created before the fix keep their long expiry on the server until they are deleted and created again.
Original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Affects Go packages
- Severity1/10Rated low by apache
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.10.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-132079 (Apache Iggy Go SDK: Go TCP client creates personal access tokens that outlive the requested expiry), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-132079 (entry last updated 2026-11-18):
Affected:
- Go package github.com/apache/iggy/foreign/go: from 0.5.0, fixed in 0.10.0
Fixed versions: 0.10.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132079 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132079 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread/16fhwkppm51x1vqr3kxo551qx2w5zpkg
- https://github.com/apache/iggy/pull/4615
- http://www.openwall.com/lists/oss-security/2026/11/18/6
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-132079
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132079"}.Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
From 0.5.0 · fixed in 0.10.0
Fixed in v0.10.0 (released Nov 4, 2026, 14 days before disclosure).
The latest release, v0.10.0, is not affected.
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | lists.apache.org · thread/16fhwkppm51x1vqr3kxo551qx2w5zpkg |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132079 |
| Record | NVD · CVE-2026-132079 |
| Write-ups 1Establishes: Technical detail and context. | |
| Link | openwall.com · lists/oss-security/2026/11/18/6 |
| Other links 1 | |
| Patch | GitHub · apache/iggy · Pull request #4615 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-132079
Is CVE-2026-132079 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-132079?
github.com/apache/iggy/foreign/go (Go): from 0.5.0 before 0.10.0.Source: cve.now feed data
How do I fix CVE-2026-132079?
Upgrade to a fixed version: 0.10.0.Source: cve.now feed data