Live › vulnerability › CVE-2026-117174

unknownOtherwithdrawn

Rejected CVE entry: duplicate of an earlier report, no product named

This CVE record was rejected by NVD and withdrawn; its only text says it duplicates VUL-2026-008368, which was reported first. No product, version or attacker capability is described.

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

Known so far

1/6

unknown

no CVSS yet; severity from the sources

known so far1 of 6

missing: versions, how to check, fix, primary source, exploitation

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

First seen by InfraStack 2026-10-29 08:23 UTC. All times on this page are UTC.

Who is affected

No product ranges from the sources yet.

How to check

Unknown from the sources.

The fix

No fix yet, per the sources.

Who had it, and when

1 source

NVD2026-10-29 08:23 UTC · published 2026-10-29 08:17 UTC · CVE-2026-117174

Each row is the first time that source carried this signal. The analyst’s rows are its own findings.

What the sources say, verbatim

›Original description, 42 characters

Rejected reason: VUL-2026-008368 為先回報之相同問題

Know the next one before it finds you.

Add to Slack

Live › vulnerability › CVE-2026-117174

unknownOtherwithdrawn

Rejected CVE entry: duplicate of an earlier report, no product named

This CVE record was rejected by NVD and withdrawn; its only text says it duplicates VUL-2026-008368, which was reported first. No product, version or attacker capability is described.

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

Known so far

1/6

unknown

no CVSS yet; severity from the sources

known so far1 of 6

missing: versions, how to check, fix, primary source, exploitation

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

First seen by InfraStack 2026-10-29 08:23 UTC. All times on this page are UTC.

Who is affected

No product ranges from the sources yet.

How to check

Unknown from the sources.

The fix

No fix yet, per the sources.

Who had it, and when

1 source

NVD2026-10-29 08:23 UTC · published 2026-10-29 08:17 UTC · CVE-2026-117174

Each row is the first time that source carried this signal. The analyst’s rows are its own findings.

What the sources say, verbatim

›Original description, 42 characters

Rejected reason: VUL-2026-008368 為先回報之相同問題

Know the next one before it finds you.

Add to Slack

Rejected CVE entry: duplicate of an earlier report, no product named

Who is affected

How to check

The fix

Who had it, and when

What the sources say, verbatim

Know the next one before it finds you.

Rejected CVE entry: duplicate of an earlier report, no product named

Who is affected

How to check

The fix

Who had it, and when

What the sources say, verbatim

Know the next one before it finds you.

Sources