CVE-2026-75907

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-24. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, ghsa
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The door access control on a Norwegian Cruise Line asset grants entry based only on the credential's static 7-byte UID stored on an NTAG212 NFC chip. A UID is a manufacturer serial number sent in the clear on every read and is not intended to be secret or to authenticate the holder. Validating on the UID of the NTAG212 NFC chip alone is identification, not authentication, and the credential has no challenge-response capability that would resist copying.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

September 24, 2026

Last Modified

September 24, 2026

Advisory Details (2)

Auto-updated Sep 24, 2026
No patch confirmed yet. Sources: cert.
cert

VU#676317 - Norwegian Cruise Line door access controller contains an improper authentication vulnerability

https://www.kb.cert.org/vuls/id/676317
cert

VU#676317 - Norwegian Cruise Line door access controller contains an improper authentication vulnerability

https://kb.cert.org/vuls/id/676317

Vendor Advisories for CVE-2026-75907(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 11× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-25 07:19 UTCEG score recompute
  2. 2026-09-25 07:19 UTCGHSA enrichment
  3. 2026-09-24 19:35 UTCEG score recompute▲ 7.50
  4. 2026-09-24 19:35 UTCGHSA enrichment
  5. 2026-09-24 19:34 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  6. 2026-09-24 18:36 UTCGHSA enrichment
  7. 2026-09-24 18:34 UTCNVD update
  8. 2026-09-24 17:17 UTCMITRE cvelistV5
  9. 2026-09-24 16:30 UTCNVD update
  10. 2026-09-24 16:02 UTCEG score recompute
  11. 2026-09-24 16:01 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-75907?
CVE-2026-75907 is a high vulnerability published on September 24, 2026. The door access control on a Norwegian Cruise Line asset grants entry based only on the credential's static 7-byte UID stored on an NTAG212 NFC chip. A UID is a manufacturer serial number sent in the clear on every read and is not intended to be secret or to authenticate the holder. Validating on…
When was CVE-2026-75907 disclosed?
CVE-2026-75907 was first published in the National Vulnerability Database on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-75907?
CVE-2026-75907 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-75907?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75907, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-75907

Explore →

Is Your Infrastructure Affected by CVE-2026-75907?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs