VulnerabilityPublished 27 Feb 2026Updated 24 Mar 2026

CVE-2025-9572: Foreman · Incorrect Authorization

Affects ForemanSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.0 Medium : upgrade to 3.16.2 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

5.0Medium

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

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

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

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

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: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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 Foreman and foreman to 3.16.2.

Affected software

Product	Affected	Fixed in
The ForemanForeman	Affected >=1.22.0 <3.16.2	Fixed in 3.16.2
Red Hatredhat/foreman`pkg:rpm/redhat/foreman`Other threats	Affected =1.22.0	Fixed in–
GitHubforeman`pkg:github/foreman`Other threats	Affected >=1.22.0 <3.16.2	Fixed in 3.16.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. 2. If you cannot patch yet, restrict network access to the Foreman GraphQL API endpoint to trusted administrators and systems only, using firewalls or network segmentation. 3. Implement strict role-based access controls (RBAC) within Foreman to minimize privileges granted to users, limiting exposure if exploited. 4. Monitor Foreman logs and network traffic for unusual GraphQL queries or access patterns that could indicate exploitation attempts. 5. Consider disabling the GraphQL API endpoint temporarily if it is not essential for operations. 6. Conduct internal audits of metadata exposure and review permissions regularly to ensure least privilege principles are enforced. 7. Stay informed through vendor advisories and security mailing lists for updates or new mitigations related to this vulnerability.

Description

n authorization flaw in Foreman's GraphQL API allows low-privileged users to access metadata beyond their assigned permissions. Unlike the REST API, which correctly enforces access controls, the GraphQL endpoint does not apply proper filtering, leading to an authorization bypass.

Impact

The primary impact of CVE-2025-9572 is unauthorized disclosure of sensitive metadata within Foreman environments. This can lead to information leakage that may assist attackers in further reconnaissance or lateral movement within an organization's infrastructure. Although the vulnerability does not allow modification or destruction of data, the exposure of metadata could reveal system configurations, network details, or other operational information that could weaken overall security posture. Organizations relying on Foreman 1.22.0 for managing critical infrastructure, especially in sectors like government, finance, telecommunications, and cloud service providers, may face increased risk of targeted attacks leveraging this information. The medium severity rating indicates a moderate risk, but the ease of exploitation and network accessibility mean that attackers with limited privileges could exploit this flaw without user interaction. This could undermine trust in the management platform and potentially lead to compliance issues if sensitive data is exposed.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Mar 2026, 00:51 UTC

Technical details

References

Community reviews

Related threats