What is CVE-2026-6484?

CVE-2026-6484 is Lack of verified boot to certain FV may cause arbitrary code execution. The supplied enrichment data classifies it as Remote Code Exec mapped to CWE-1277 CWE-1277.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-6484. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-6484 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

4 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-6484 using CVSS 8.2, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

highRemote Code Execpublic exploit

CVE-2026-6484

CVE-2026-6484 — Lack of verified boot to certain FV may cause arbitrary code execution

In an UEFI, Lack of verified boot to certain FV may cause arbitrary code execution.

Published Aug 12, 2026Updated Aug 12, 2026Sources: NVD, Insyde Software (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

Insyde Software

InsydeH2O

CVSS base

8.2

high

Remediation

The vendor's own words where we have them.

Intel Mobile Platforms: Panther Lake: Unaffected Lunar Lake: Unaffected Aarow Lake H/U: Version 05.56.17.0022 Aarow Lake S/HX: Version 05.56.17.0037 Rapter Lake: Version 05.47.24.0058 Twin Lake: Version 05.44.45.0029 Intel Server/Embedded platforms: Whitley (CLX/CPX/ICX): Trunk CedarIsland (CPX): Trunk Eagle Stream: Unaffected Birch Stream: Unaffected Mehlow/Mehlow-R(CFL-S): Unaffected Tatlow (RKS): Unaffected Jacobsville(SNR): Trunk Idaville: Trunk Kaseyville: Unaffected Whiskey Lake: Trunk Come tLake-S: Unaffected Tiger Lake UP3/H: Unaffected Alder Lake: Version 05.47.24.2057 Raptor Lake: V…

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Insyde Software	InsydeH2O	See in the Solution	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Changed

Attack Complexity

Low

Attack Vector

Local

Privileges Req

High

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
8.2	CVSS 3.1	high	1.5	6	CNA, Insyde Software (CNA)

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

Weakness & attack patterns

CWE-1277

Inferred from the weakness class — not observed against this CVE.

CAPEC-242 · Code InjectionCAPEC-35 · Leverage Executable Code in Non-Executable Files

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Monitor for scanner or exploit-pattern traffic after 4 public PoC repositories were reported.

EDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 8.2 (AV:L)
Aug 12, 2026 · NVD
Initial · CVE published
Aug 12, 2026 · NVD

References

1 on the record

www.insyde.com/security-pledge/sa-2026003/
Vendor Advisory

Elsewhere on this site

Insyde Softwareevery CVE for this vendor
Remote Code Execsame class
CWE-1277other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-6484 is Lack of verified boot to certain FV may cause arbitrary code execution, a high vulnerability affecting InsydeH2O from Insyde Software. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-6484. Public exploit evidence is: 4 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.2 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.