5.5

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2025-59036

CVE-2025-59036: 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.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2025-59036

CVE-2025-59036:

5.5

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
infrahub-server	pip	< 1.3.9	1.3.9
infrahub-server	pip	>= 1.4.0, < 1.4.5	1.4.5

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability lies in the authentication logic for API tokens in Infrahub. The root cause is twofold: the system failed to check if a token had been deleted, and it failed to check if a token had expired. This allowed any API token, even if deleted or expired, to grant access as long as the user account it was associated with was still active.

The analysis of the provided patches pinpoints the exact location of these flaws within the AccountTokenValidatorQuery class in backend/infrahub/core/account.py.

Deleted Tokens: The query_init method was responsible for building the database query to find a token. The original query did not include a condition to check if the token's status was 'active'. The patch rectifies this by adding WHERE r1.status = "active" AND r2.status = "active" clauses, effectively filtering out any tokens that have been marked as deleted.
Expired Tokens: The get_account_id method was responsible for returning the user's ID after the token was found. The original implementation performed no check on the token's expiration date. The patch introduces logic to fetch the expiration timestamp, compare it to the current time, and return None if the token is expired.

The function validate_token is the higher-level function that uses this vulnerable class, and it would appear in a stack trace during an exploit attempt. Therefore, monitoring calls to validate_token and the methods of AccountTokenValidatorQuery would be key to detecting exploitation of this vulnerability.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.