How severe is GHSA-h5fq-653g-gxrm?

GHSA-h5fq-653g-gxrm has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-h5fq-653g-gxrm?

GHSA-h5fq-653g-gxrm affects the following packages: github.com/Luzifer/ots (Go). Ecosystems affected: Go.

How do I fix GHSA-h5fq-653g-gxrm?

Update github.com/Luzifer/ots to 1.21.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h5fq-653g-gxrm is resolved across your whole dependency graph.

How do I detect GHSA-h5fq-653g-gxrm in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/Luzifer/ots, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-h5fq-653g-gxrm if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-h5fq-653g-gxrm actively exploited in the wild?

No public exploit code has been indexed for GHSA-h5fq-653g-gxrm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-h5fq-653g-gxrm published, and has it been updated?

GHSA-h5fq-653g-gxrm was published on May 5, 2026 and was last updated on July 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

ots has a negative expire override that can bypass its secret retention policyGHSA-h5fq-653g-gxrm

MEDIUMFix: Luzifer/ots@3511bd1

GHSA-h5fq-653g-gxrm is a medium-severity (CVSS 5.3) vulnerability in github.com/Luzifer/ots. A fix is available for github.com/Luzifer/ots — see the affected versions and patch details below.

Also known asGO-2026-5413

Published

May 5, 2026

Updated

Jul 21, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 21, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/Luzifer/ots

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

The /api/create endpoint accepted negative expire query values. For the memory storage backend, negative values were passed to secret creation as a negative duration and treated as no expiry, allowing callers to create secrets that persisted longer than intended.

Impact

Unauthenticated users could bypass configured retention expectations for secrets they create by sending POST /api/create?expire=-1.

This does not allow reading or modifying secrets created by other users. Secrets remain one-time-read and, in the normal web flow, client-side encrypted.

Affected versions

Versions up to and including v1.21.4 are affected.

Patched versions

Fixed in v1.21.5.

Workarounds

Disable expiry overrides via disableExpiryOverride: true until upgrading.

Credit

Reported by Chai Cheng Xun via email.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/Luzifer/ots`	all versions	1.21.5`go get github.com/Luzifer/ots@v1.21.5`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/Luzifer/ots, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/Luzifer/ots to 1.21.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h5fq-653g-gxrm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

## Summary The `/api/create` endpoint accepted negative `expire` query values. For the memory storage backend, negative values were passed to secret creation as a negative duration and treated as no expiry, allowing callers to create secrets that persisted longer than intended. ## Impact Unauthenticated users could bypass configured retention expectations for secrets they create by sending `POST /api/create?expire=-1`. This does not allow reading or modifying secrets created by other users. Secrets remain one-time-read and, in the normal web flow, client-side encrypted. ## Affected versio

O3 Security · Impact-Aware SCA

Is GHSA-h5fq-653g-gxrm in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works