Unknown severity · Source severity not reportedCVE-2026-62178

CVE-2026-62178

Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-61427. Reason: This candidate is a duplicate of CVE-2026-61427. Notes: All CVE users should reference CVE-2026-61427 instead of this candidate.

Published Jul 15, 2026Updated Jul 15, 2026Source checked Jul 18, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: No known exploitation
Affected software: Not mapped
Fix availability: Not reported

Recommended action

Review the upstream advisory, identify the affected product in your inventory, and apply the vendor update when one is available.

What this means

CVE-2026-62178 is listed in the HOL Guard supply-chain feed, but affected software is not mapped to a package. Review the upstream advisory for the affected product and vendor guidance. Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-61427. Reason: This candidate is a duplicate of CVE-2026-61427. Notes: All CVE users should reference CVE-2026-61427 instead of this candidate.

Affected software

Affected software not mapped. Review the upstream record for vendor-specific product and version guidance.

Evidence and references

No references were reported by the source.

Source metadata

Published: Jul 15, 2026
Modified: Jul 15, 2026
Source checked: Jul 18, 2026

Reported by NVD (nvd).

Keep this signal in your Guard workflow.

HOL Guard can help your team monitor supply-chain activity while the upstream record is clarified.

Explore HOL Guard

Back to active CVEs