CVE-2025-59036VulnerabilityPublished 9 Sep 2025

CVE-2025-59036: opsmill infrahub · Improper Validation of Certificate Expiration

Affects opsmill infrahubSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium : upgrade to 1.3.9 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.3.9

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade opsmill infrahub to 1.3.9.

Affected software

Product	Affected	Fixed in
opsmill infrahub	Affected <1.3.9	Fixed in 1.3.9

AI-suggested

To mitigate this vulnerability, European organizations should promptly upgrade Infrahub to versions 1.3.9 or 1.4.5 where the issue is fixed. Until upgrades can be applied, organizations should implement the recommended workaround by identifying and deleting or deactivating user accounts associated with deleted or expired API tokens to prevent token reuse. Additionally, organizations should audit API token usage and implement strict token lifecycle management policies, including regular token expiration and revocation processes. Monitoring and alerting on unusual API authentication attempts can help detect exploitation attempts early. Enforcing multi-factor authentication (MFA) for user accounts with API token access and limiting token privileges to the minimum necessary can further reduce risk. Network segmentation and access controls should restrict Infrahub API access to trusted hosts and users only. Finally, organizations should review and update incident response plans to include scenarios involving compromised API tokens.

Description

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 and/or expired to be considered valid. This means that any API token that is associated with an active user account can authenticate successfully. This issue is fixed in versions 1.3.9 and 1.4.5. As a workaround, users can delete or deactivate the account associated with a deleted API token to prevent that token from authenticating.

Impact

For European organizations, the impact of this vulnerability can be significant, especially for those relying on Infrahub for critical infrastructure automation and management. Unauthorized access via stale API tokens could lead to exposure of sensitive operational data, unauthorized modification of automation playbooks, or disruption of infrastructure management processes. This could result in operational downtime, data breaches, or compliance violations under regulations such as GDPR. Organizations in sectors like finance, healthcare, manufacturing, and critical infrastructure, which often use automation tools like Infrahub, may face increased risk. The medium severity rating reflects a moderate risk level, but the potential for lateral movement or privilege escalation within the environment could amplify the consequences. The requirement for some privilege and user interaction reduces the likelihood of widespread exploitation but does not eliminate risk, especially from insider threats or compromised accounts.

CWE-298Improper Validation of Certificate Expiration (opens in a new tab)
Variant weaknessLikelihood of exploit: LowOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
A certificate expiration is not validated or is incorrectly validated.
Architecture and Design
Check for expired certificates and provide the user with adequate information about the nature of the problem and how to proceed.
Implementation
If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the expiration.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/opsmill/infrahub/security/advisories/GHSA-v2p7-4pv4-3wwh (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Sep 2025, 00:55 UTC

WeaknessesCWE-298

Technical details

References

Community reviews

Related threats