Infrahub: Deleted and expired API tokens can still authenticate
### Impact A bug in the authentication logic will cause API tokens that were deleted and/or expired to be considered valid. This means that any API token that is associated with an active user account can authenticate successfully. ### Patches This issue is fixed in versions `1.3.9` and `1.4.5` ### Workarounds Users can delete or deactivate the account associated with a deleted API token to prevent that token from authenticating.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-59036US | — | — | ||
Infrahub offers a central hub to manage data, templates, and playbooks. Prior to versiond 1.3.9 and 1.4.5, a bug in the authentication logic will cause API tokens that were deleted… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/opsmill/infrahubPACKAGE
- https://github.com/opsmill/infrahub/commit/215185f217e2f754f7c0a0aa4b77e11079a063a1WEB
- https://github.com/opsmill/infrahub/commit/61b49a4a9e988f10c3a44f0e86ef97f344a1e228WEB
- https://github.com/opsmill/infrahub/releases/tag/infrahub-v1.3.9WEB
- https://github.com/opsmill/infrahub/releases/tag/infrahub-v1.4.5WEB
- https://github.com/opsmill/infrahub/security/advisories/GHSA-v2p7-4pv4-3wwhWEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-59036ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan