CVE-2026-6484General

LOWCVSS 8.2 · HIGH

Signal is active with 2 mentions in latest observed window

Immediate actions

  • Patch affected systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

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

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-1277

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Threat summary

  • Patch or workaround signal is available
  • 2 mentions across 1 observed day

What's happening

  • Patch or workaround mentioned in 1 signal
  • General: 1 classified signal
  • 2 total mentions across 1 day

Deep dive

Activity timeline2 mentions / 1d
01122Mentions · 2026-08-11: 2Patch / Workaround · 2026-08-11: 108-11
Signal classification2 categories
General
150.0%
Patch
150.0%
Full discourse2 posts
  • Nikolaj Schlej@NikolajSchlej
    General

    Turns out this tweet thread of mine ended up getting CVE-2026-6484 and Insyde SA-2026003. I've also worked with several OEMs to correctly address the vulnerability, but it sadly remains in quantum superposition of fixed and unfixed until the BIOS image is observed by UEFITool NE.

    Post summary

    The tweet mentions CVE-2026-6484 but provides no technical details, exploit code, or patch information, leaving its status unclear.

    2101641.3K
    4.3K followersView on X
  • Nikolaj Schlej@NikolajSchlej
    Patch

    Case in point for the quantum thing: Lenovo lists CVE-2026-6484 as fixed for some new images, out of which some are truly fixed (additional volumes are removed or hashed/verified), some are partially fixed (one volume is removed or hashed/verified, the one one remains vulnerable)

    Post summary

    Lenovo has applied fixes for CVE‑2026‑6484, with some firmware images fully patched and others partially patched by removing hashed volumes.

    10010191
    4.3K followersView on X

Explore more