Skip to main content
VulnerabilityPublished

CVE-2026-132079: Insufficient Session Expiration Vulnerability

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-132079· High

Not known to be exploited : upgrade to 0.10.0 soon.

Data as of 18 Nov 2026, 13:52 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 0.10.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade Apache Iggy Go SDK and github.com/apache/iggy/foreign/go to 0.10.0.

Affected software

ProductAffectedFixed in
Apache Iggy Go SDKgithub.com/apache/iggy/foreign/goAffected
  • >=0.5.0 <0.10.0
Fixed in
  • 0.10.0
Gogithub.com/apache/iggy/foreign/gopkg:golang/github.com/apache/iggy/foreign/goOther threatsAffected
  • >=0.5.0 <0.10.0
Fixed in
  • 0.10.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Apache Iggy Go SDK to version 0.10.0 or later, which fixes the session expiration encoding issue. Additionally, revoke and delete any personal access tokens created with affected versions, then generate new tokens to ensure proper expiration enforcement.

Description

The Apache Iggy Go SDK versions from 0.5.0 up to but not including 0.10.0 contain an insufficient session expiration vulnerability. The CreatePersonalAccessToken method incorrectly encodes the token expiry time, causing the server to interpret the expiry as approximately four billion times longer than intended. This results in tokens remaining valid far beyond their expected lifetime. Version 0.10.0 addresses this issue. Users should upgrade and revoke any tokens created with affected versions to mitigate the risk.

References

Community reviews

Loading reviews…