External risk intelligence

Apache Iggy Go SDK Extended Token Expiration Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-132079

The vulnerability exists in a Go SDK (client library) used to build applications that communicate with the Apache Iggy server. While the resulting tokens are used in network communications, the flaw is located within the development-side code or client implementation logic, rather than an exposed internet-facing service or appliance itself. Direct exposure is uncommon as it relies on specific client-side code integration.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability involves an issue with how session expiration is handled in the Apache Iggy Go SDK, potentially causing tokens to remain valid for an excessively long period. This could allow unauthorized access to systems if not properly managed.

  • Session tokens may not expire as intended.
  • This affects how applications authenticate users.
  • Review token management and update SDKs.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this by creating a personal access token using the vulnerable Go SDK. This token, when used to connect to the Apache Iggy server, would be valid for an extremely extended period, approximately four billion times longer than intended. This prolonged access could then be leveraged for further malicious activities.

  • Unauthenticated network access required.
  • Vulnerable token creation method.
  • Extended access for data compromise.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow tokens to remain valid for an extended period, approximately four billion times longer than intended, when created using the Apache Iggy Go SDK. This prolonged validity could affect the intended lifecycle of access tokens.

  • Access tokens.
  • Long-lived tokens could be misused.
  • Unauthorized access to resources.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Apache Iggy Go SDK's session expiration flaw requires attention from development teams responsible for applications integrating with Iggy, and potentially platform or infrastructure teams managing Iggy instances. The first practical step is to identify applications using the affected SDK, confirm their network exposure, and then determine the business criticality of those integrations to prioritize remediation efforts with the accountable application owner.

  • Application development teams should own the fix.
  • Verify applications using the affected SDK.
  • Redeploy applications with updated SDK.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Apache Iggy Go SDK?

The Apache Iggy Go SDK is a set of tools that developers use to build applications that communicate with an Apache Iggy server. It provides the necessary functions for client-side code to interact with the message streaming platform, including features for authentication like managing personal access tokens.

How does CVE-2026-132079 affect token expiration?

This vulnerability, classified as CWE-613 (Insufficient Session Expiration), occurs when the SDK incorrectly writes the token's expiry time into memory. Due to this calculation error, the server interprets the requested duration as being billions of times longer than intended, effectively causing the authentication tokens to remain valid almost indefinitely.

Do I need to trigger the bug to create a faulty token?

Yes, the bug is specifically triggered when a developer uses the TCP client method 'CreatePersonalAccessToken' within the affected SDK versions (0.5.0 through 0.9.x). If your application does not use this specific method to generate tokens, it will not experience this faulty extended expiration behavior.

Is my system at risk if it uses this SDK?

According to Halo Surface Signal, this vulnerability exists in a client-side library, not an internet-facing appliance itself. While the tokens themselves are used over the network, direct exposure is unlikely unless your custom-built application logic is directly accessible, as the risk depends on how your specific code integrates with the SDK.

Why should I delete old tokens after updating the SDK?

Updating the SDK to version 0.10.0 prevents new tokens from having this issue, but it cannot fix tokens already stored on the server. Because tokens created by older versions retain their extended validity even after an update, you must manually delete those existing tokens and generate fresh ones to restore proper session security.

References