Skip to main content
CVE-2024-38798VulnerabilityPublished

CVE-2024-38798: TianoCore EDK2 · Information Exposure

Affects TianoCore EDK2Source CVE Database V5

0

Not known to be exploited · CVSS 5.8 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score
5.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:L/VA:L/SC:L/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubtianocore/edk2pkg:github/tianocore/edk2Other threatsAffected
  • =0
Fixed in–

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

AI-suggested

1. Restrict and monitor physical and local access to systems running vulnerable EDK2 firmware to reduce the risk of local exploitation. 2. Implement strict access controls and logging on endpoints to detect and respond to suspicious local activities promptly. 3. Employ hardware-based security features such as TPM and secure boot to limit unauthorized firmware modifications and information disclosure. 4. Maintain up-to-date inventory of hardware and firmware versions to identify affected systems accurately. 5. Engage with hardware vendors and TianoCore project for timely patches or firmware updates once available, and prioritize deployment in critical environments. 6. Conduct regular security audits and penetration testing focusing on firmware and BIOS security to uncover potential exploitation paths. 7. Educate IT and security staff about the risks of local attacks on firmware and the importance of physical security controls. 8. Consider deploying endpoint detection and response (EDR) solutions capable of monitoring low-level system behaviors indicative of firmware exploitation attempts.

Description

EDK2 contains a vulnerability in BIOS where an attacker may cause “Exposure of Sensitive Information to an Unauthorized Actor” by local access. Successful exploitation of this vulnerability will lead to possible information disclosure or escalation of privilege and impact Confidentiality.

References

Community reviews

Loading reviews…