Dell Alienware Command Center (AWCC)

Not in CISA KEVCVE-2026-91898CWE-347

Not confirmed exploited. No WAF vendor names it yet.

Edge rules

0/8

Our test

No exploit yet

CVSS

8.1

EPSS

—

Posts, 14d

Published

2026-11-02

Dell Alienware Command Center (AWCC), versions prior to 6.14.54.0, contain an Improper Verification of Cryptographic Signature vulnerability. An unauthenticated attacker with adjacent network access could potentially exploit this… More

Edge coverage

Claimed by vendors

CloudflareNo public claimNot named AWSNo public claimNot named Microsoft AzureNo public claimNot named Google CloudNo public claimNot named FastlyNo public claimNot named F5No public claimNot named AkamaiNo public sourceNo public changelog OWASP CRSNo public claimNot named

Ask Vigil

AI · answers from this page

Ask about CVE-2026-91898: who's covered, what to patch first, how vendors compare. I cite sources and won't help with attacks.

Workers AI (Llama 3.3). Can be wrong: check the cited source.

Severity, decoded

CVSS 3.1

8.1High

High · 8.1 / 10

Exploitable over the network under specific conditions, with no privileges and no user interaction, leading to full loss of confidentiality, integrity and availability.

Over the internetNo login neededNo user actionHard to pull offFull compromise

How the score is built8 metrics

Attack vectorAn attacker can reach it over the internet; no access to your network needed.
Network
Attack complexityThe attack only works when conditions outside the attacker's control line up.
High
Privileges requiredNo account or login is needed.
None
User interactionNo one has to click or open anything; the attack works on its own.
None
ScopeThe damage stays within the vulnerable component.
Unchanged
Confidentiality impactAn attacker can read all data the affected component holds, or the most sensitive parts of it.
High
Integrity impactAn attacker can change any data or files the affected component protects.
High
Availability impactAn attacker can take the component down completely or keep it from serving anyone.
High

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

Public exploits

None found

0 Metasploit0 Exploit-DB0 Scanner template0 GitHub PoCs

No exploit in Exploit-DB or Metasploit, and no scanner template. That lowers, but doesn't remove, the chance of mass exploitation.

Timeline

2026-11-02
CVE published
CVE List
2026-11-02
First social mention we saw

Vendor statements

Quoted

CloudflareWAF Managed RulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Each row gives the rule ID and its default action. The feed starts in January 2025, so older rules are missing.

AWSAWS WAF Managed RulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.

Microsoft AzureFront Door and Application Gateway WAF (DRS)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.

Google CloudCloud Armor preconfigured WAF rulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Google names few CVEs: the release notes start in May 2024 and the rules reference lists CVEs without dates. Its cve-canary rules are opt-in.

FastlyNext-Gen WAF virtual patchesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The feed holds only the latest 25 changes, so history builds up from the day we started reading it.

F5Attack signatures (Distributed Cloud WAF)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Each signature lists the CVEs it references, with its id and date. F5 does not state a default action; signatures enforce once staging ends in your policy.

AkamaiApp & API Protector (Adaptive Security Engine)No public source

This vendor publishes no machine-readable rule changelog we can check.

OWASP CRSCore Rule Set (open source, used inside many WAFs)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.