What is the fix for CVE-2026-117830?

No action needed; the record is withdrawn. Remove any tracker entry or scanner finding that references CVE-2026-117830 and confirm the advisory source.

Live › vulnerability › CVE-2026-117830

Go to dashboard

unknownOtherwithdrawn

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

This CVE identifier was reserved by mistake and was later rejected by NVD. The record states it was never associated with a real vulnerability.

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

Known so far

2/6

unknown

no CVSS yet; severity from the sources

known so far2 of 6

missing: versions, how to check, 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 vulnerability is described, so no attacker outcome applies.
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-117830

Go to dashboard

unknownOtherwithdrawn

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

This CVE identifier was reserved by mistake and was later rejected by NVD. The record states it was never associated with a real vulnerability.

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

Known so far

2/6

unknown

no CVSS yet; severity from the sources

known so far2 of 6

missing: versions, how to check, 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 vulnerability is described, so no attacker outcome applies.
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-117830 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-117830 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