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

Published Nov 18, 2026
·
Updated

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.

Affected Software

1 affected component
Apache Iggy Go SDK>=0.5.0<0.10.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 0.10.0
  2. Operational

    Delete personal access tokens created by an earlier affected version and create new ones; those tokens retain their long expiry on the server.

Event History

Nov 18, 2026
CVE Published
via MITRE·11:57 AM
Data Sourced
via MITRE·11:57 AM
DescriptionWeakness
Data Sourced
via NVD·12:17 PM
DescriptionWeakness

Frequently Asked Questions

1

Who is affected by this issue?

Applications using the Apache Iggy Go SDK TCP client to create personal access tokens are affected if they use versions from 0.5.0 before 0.10.0. Tokens created by other methods are not identified as affected by the provided information.

2

What does an attacker need to exploit this?

An attacker would need access to a personal access token created through the affected Go TCP client. The issue causes that token to remain valid far beyond the expiry requested by its creator.

3

Does upgrading revoke tokens that were already created?

No. Tokens created by an affected earlier version retain their overly long server-side expiry after the SDK is upgraded. Delete those tokens and create new ones.

4

What should be done if affected tokens may exist?

Upgrade to Apache Iggy Go SDK version 0.10.0, then identify and delete personal access tokens created through earlier affected Go TCP client versions. Recreate any required tokens with the fixed SDK.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203