CVE-2024-6861VulnerabilityPublished 6 Nov 2024Updated 20 Nov 2025

CVE-2024-6861: Information Exposure

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 6 Nov 2024
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-25.

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

AI-suggested

1. Immediately disable the GraphQL introspection feature in Foreman if it is enabled in production environments, as this feature is primarily intended for development and debugging. 2. Implement strict network access controls to restrict API access to trusted internal networks or VPNs, minimizing exposure to external attackers. 3. Monitor Foreman API logs for unusual access patterns or queries that may indicate attempts to exploit introspection. 4. Stay updated with Foreman vendor advisories and apply security patches promptly once released to address this vulnerability. 5. Employ API gateway or web application firewall (WAF) rules to detect and block suspicious GraphQL introspection queries. 6. Rotate admin authentication keys and credentials regularly, especially if exposure is suspected. 7. Conduct security audits and penetration testing focused on API security to identify and remediate similar configuration weaknesses. 8. Educate development and operations teams about the risks of enabling introspection in production and enforce secure configuration baselines.

Description

A disclosure of sensitive information flaw was found in foreman via the GraphQL API. If the introspection feature is enabled, it is possible for attackers to retrieve sensitive admin authentication keys which could result in a compromise of the entire product's API.

Impact

The primary impact of CVE-2024-6861 is the unauthorized disclosure of sensitive administrative authentication keys, which can lead to a complete compromise of the Foreman API. Attackers gaining these keys can perform administrative operations, potentially manipulating infrastructure configurations, deploying malicious changes, or extracting further sensitive data. This breach of confidentiality can cascade into broader organizational security incidents, including lateral movement within networks and disruption of critical IT management processes. Since no authentication or user interaction is required, the attack surface is wide, increasing the likelihood of exploitation. Organizations relying on Foreman for infrastructure automation and management face risks to operational integrity indirectly, as attackers could alter configurations or disable security controls. The absence of known exploits currently limits immediate widespread impact, but the vulnerability’s nature makes it a prime target for attackers once exploit code becomes available. The impact is global, affecting any organization using vulnerable Foreman versions with introspection enabled, especially those in sectors with high-value infrastructure such as government, finance, and critical manufacturing.

References

Community reviews

Loading reviews…