{"answers":{"affected":"3 open source packages ship an affected version, including github.com/Luzifer/ots.","exploited":"There is no known exploitation of GHSA-h5fq-653g-gxrm in the wild and no public exploit code.","fix":"Upgrade github.com/Luzifer/ots to 1.21.5 or later.","what":"GHSA-h5fq-653g-gxrm is a vulnerability in github.com/Luzifer/ots, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-h5fq-653g-gxrm and fix it if it is affected.\n\nWhat it is: GHSA-h5fq-653g-gxrm is a vulnerability in github.com/Luzifer/ots, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-h5fq-653g-gxrm in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/Luzifer/ots (Go): affected all versions; fixed in 1.21.5\n- github.com/Luzifer/ots (Go): affected all versions; fixed in 1.21.5\n- github.com/Luzifer/ots (Go): affected all versions; fixed in 1.21.5\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-h5fq-653g-gxrm/ (Markdown: https://insights.sbomify.com/GHSA-h5fq-653g-gxrm/index.md)","id":"GHSA-h5fq-653g-gxrm","markdown":"https://insights.sbomify.com/GHSA-h5fq-653g-gxrm/index.md","name":"GHSA-h5fq-653g-gxrm","record":{"aliases":["GO-2026-5413"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Go secret storage","requires_auth":"none","summary":"Unauthenticated attackers can bypass secret retention policies by sending negative expiry values, causing secrets to persist longer than intended.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"## Summary\n\nThe `/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.\n\n## Impact\n\nUnauthenticated users could bypass configured retention expectations for secrets they create by sending `POST /api/create?expire=-1`.\n\nThis 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.\n\n## Affected versions\n\nVersions up to and including v1.21.4 are affected.\n\n## Patched versions\n\nFixed in v1.21.5.\n\n## Workarounds\n\nDisable expiry overrides via `disableExpiryOverride: true` until upgrading.\n\n## Credit\n\nReported by Chai Cheng Xun via email.","ecosystems":["Go"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"ots has a negative expire override that can bypass its secret retention policy","id":"GHSA-h5fq-653g-gxrm","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Go","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"Go","fixed":["1.21.5"],"introduced":["0"],"last_affected":[],"package":"github.com/Luzifer/ots","purl":null,"source":"GHSA-h5fq-653g-gxrm"},{"ecosystem":"Go","fixed":["1.21.5"],"introduced":["0"],"last_affected":[],"package":"github.com/Luzifer/ots","purl":"pkg:golang/github.com/Luzifer/ots","source":"GHSA-h5fq-653g-gxrm"},{"ecosystem":"Go","fixed":["1.21.5"],"introduced":["0"],"last_affected":[],"package":"github.com/Luzifer/ots","purl":"pkg:golang/github.com/Luzifer/ots","source":"GO-2026-5413"}],"products":null,"published":"2026-05-05","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Unauthenticated attackers can bypass secret retention policies by sending negative expiry values, causing secrets to persist longer than intended.","url":"https://insights.sbomify.com/GHSA-h5fq-653g-gxrm/"}