How do I check whether I am affected by CVE-2026-117827?

- Look up the identifier at https://nvd.nist.gov/vuln/detail/CVE-2026-117827 and confirm the status is rejected.

What is the fix for CVE-2026-117827?

- No action needed; the identifier was withdrawn and does not describe a vulnerability to patch.

Live › vulnerability › CVE-2026-117827

unknownOtherwithdrawn

CVE-2026-117827 was reserved in error and never describes a vulnerability

This CVE identifier was reserved by mistake and was later rejected by NVD, so no real flaw is attached to it. There is no attacker capability to describe.

Summary written from the sources below. Check the originals before acting.

Known so far

3/6

unknown

no CVSS yet; severity from the sources

known so far3 of 6

missing: versions, primary source, exploitation

First public: Oct 28, 2026 UTC
Last modified: Oct 28, 2026
Status: withdrawn
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-28 11:32 UTC. All times on this page are UTC.

Why it is unknown, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: Not known from the sources.
Needs a special setup: Not known from the sources.
Reachable from: Not known from the sources.
Worst case: No attacker capability; the record describes no flaw.
CVSS said: No score. The facts above say low; we keep the sources' unknown until an analyst looks.

Who is affected

No product ranges from the sources yet.

Know the next one before it finds you.

Add to Slack

Live › vulnerability › CVE-2026-117827

Go to dashboard

unknownOtherwithdrawn

CVE-2026-117827 was reserved in error and never describes a vulnerability

This CVE identifier was reserved by mistake and was later rejected by NVD, so no real flaw is attached to it. There is no attacker capability to describe.

Summary written from the sources below. Check the originals before acting.

Known so far

3/6

unknown

no CVSS yet; severity from the sources

known so far3 of 6

missing: versions, primary source, exploitation

First public: Oct 28, 2026 UTC
Last modified: Oct 28, 2026
Status: withdrawn
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-28 11:32 UTC. All times on this page are UTC.

Why it is unknown, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: Not known from the sources.
Needs a special setup: Not known from the sources.
Reachable from: Not known from the sources.
Worst case: No attacker capability; the record describes no flaw.
CVSS said: No score. The facts above say low; we keep the sources' unknown until an analyst looks.

Who is affected

No product ranges from the sources yet.

Know the next one before it finds you.

Add to Slack

CVE-2026-117827 was reserved in error and never describes a vulnerability

Why it is unknown, and not just CVSS

Who is affected

Know the next one before it finds you.

CVE-2026-117827 was reserved in error and never describes a vulnerability

Why it is unknown, and not just CVSS

Who is affected

Know the next one before it finds you.

How to check

The fix

Who had it, and when

What the sources say, verbatim

Sources