WhatBrokeToday
GTA 6FAQ
Apache

Apache Iggy Go SDK Insufficient Session Expiration Vulnerability

critical

Is it fixed? Not yet.

Ongoing since Nov 18, 12:17 UTC. First reported Nov 18, 12:17 UTC.

What happened

An insufficient session expiration vulnerability exists in the Apache Iggy Go SDK where the TCP client method CreatePersonalAccessToken incorrectly writes the 32-bit expiry into the upper half of the 64-bit expiry field. As a result, tokens created through the Go TCP client stay valid approximately four billion times longer than requested. The issue affects versions 0.5.0 up to 0.10.0.

What caused it?

The TCP client method CreatePersonalAccessToken wrote the 32-bit expiry into the upper half of the 64-bit expiry field read by the server, causing the server to interpret a nonzero expiry as 2^32 times the requested value.

Source: tenable.com

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Official fix

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on security advisory

    Apache Iggy Go SDK.: CVE-2026-132079 (Critical)

    Source

Evidence

1 report · 1 CVEShow
  1. [1]
    CVE First report
    Apache Iggy Go SDK.: CVE-2026-132079 (Critical)(opens security advisory in a new tab)

    Critical severity. 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…

    by Tenable 0upvotes 0comments

FAQ

What happened in the Apache issue?

An insufficient session expiration vulnerability exists in the Apache Iggy Go SDK where the TCP client method CreatePersonalAccessToken incorrectly writes the 32-bit expiry into the upper half of the 64-bit expiry field. As a result, tokens created through the Go TCP client stay valid approximately four billion times longer than requested. The issue affects versions 0.5.0 up to 0.10.0.

What is affected by the Apache issue?

Apache (versions: 0.5.0 before 0.10.0).

When did the Apache issue start and end?

It started Nov 18, 12:17 UTC and is still ongoing (16 h 26 min so far). This page updates as it develops.

How do I get alerts for Apache?

Subscribe to the Apache RSS feed for every new Apache incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Apache is down. Apache feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.