Skip to main content

NCL Door Access CVE-2026-75907

| EUVDEUVD-2026-86156 HIGH
Improper Authentication (CWE-287)
2026-09-24 certcc GHSA-x9r9-43q5-jgwv
7.5
CVSS 3.1 · Vendor: certcc
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Approach victim carrying NFC keycard
  2. Delivery
    Skim cleartext NTAG212 UID via reader
  3. Exploit
    Clone UID to blank/emulator card
  4. Execution
    Present clone at door reader
  5. Impact
    Gain unauthorized physical entry

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK

2 techniques across 2 tactics: Defense Evasion, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires physical/NFC proximity to a legitimate credential: the attacker must be close enough (typically a few centimeters) to skim the static 7-byte UID from a victim's NTAG212 chip, then must physically present the cloned credential at a Norwegian Cruise Line door reader. The limiting factors are (1) physical access to both the target credential and the door, and (2) the credential using an NTAG212 with no challenge-response - the flaw is inherent to the access-control design, so it affects the deployed system by default rather than a toggled configuration. The CVSS AV:N (network) metric overstates reachability; realistic exploitation is proximity-based, not remote.

Impact

The vendor/NVD CVSS of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) is internally inconsistent with the described vulnerability and should be treated with skepticism. The flaw is that a shipboard door access control authenticates solely on the static, cleartext 7-byte UID of an NTAG212 NFC chip - a manufacturer serial number that is trivially readable and clonable. This is fundamentally a proximity/physical attack, not a network one: an attacker must NFC-read a legitimate credential (centimeter-range) and then present a cloned card at a physical door. The AV:N (network) metric is therefore almost certainly wrong - this should be AV:P or AV:A. Likewise the impact modeling is questionable: the real consequence is unauthorized physical entry (an integrity/access-control failure, arguably I:H), yet the vector reports C:H/I:N/A:N. On real-world signals: no EPSS score, no CISA KEV listing, and no public POC are provided, so this is 'no public exploit identified at time of analysis.' No SSVC decision data was supplied. Net assessment: despite the 7.5 'High' label, this is a low-urgency, single-organization physical-security design weakness rather than a scalable remote threat - the network vector inflates the score. Verify the true attack vector with CERT/CC (VU#676317), as CVSS indicates network access but the description clearly implies physical/NFC proximity.

Exploit ScenarioDerived

An attacker discreetly reads the cleartext UID of a passenger's or crew member's NTAG212 keycard using a cheap handheld NFC reader while in close proximity, then writes that UID to a blank/emulator NFC card. Presenting the clone at the door reader grants entry because the system only checks the static UID and has no challenge-response. No public exploit code is required - UID cloning is a well-known, commodity NFC technique.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 24, 2026

Door access control readers operated by Norwegian Cruise Line grant entry based solely on the static 7-byte UID of an NTAG212 NFC credential, so anyone who can read that UID can reproduce a working key to the ship's doors. Because the UID is a manufacturer serial number transmitted in the clear during every read and the NTAG212 has no challenge-response capability, the weakness is intrinsic to the access-control design and present by default rather than a toggled configuration, affecting every credential and reader pair deployed in this scheme. NVD rates the issue 7.5, but the supplied vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) is internally inconsistent with the physical nature of the attack; our independent assessment re-scores it as CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, reflecting proximity-based exploitation with full integrity impact on door state. Exploitation requires close-range skimming of a victim's NTAG212 chip (typically a few centimetres) followed by physically presenting the cloned credential at a reader, and no public exploit code has been identified at time of analysis.

RemediationAI

No vendor-released patch has been identified at time of analysis, and none is expected from firmware alone: because the flaw is inherent to UID-only validation, the only complete fix is replacing the NTAG212 credential scheme with tags that support cryptographic challenge-response and reader-side key verification, such as MIFARE DESFire EV2/EV3 or HID Seos credentials, which requires replacing both cards and readers. Until that migration completes, apply compensating controls in order of effectiveness: (1) introduce a second independent factor at the door - a PIN, mobile credential, or QR/TOTP entry code - so a cloned UID alone is insufficient; (2) if the readers support card-authentication modes (SIO/SAM), enable them and disable any UID-only fallback, accepting that legacy NTAG212 cards will stop working and must be reissued; (3) staff sensitive doors (engine rooms, bridges, crew quarters, stores) with human verification or mechanical key overrides, at the cost of throughput and headcount; (4) enable and monitor reader logs for duplicate or impossible UID sequences (same UID at two readers within an implausible interval) and treat such events as cloning incidents; and (5) reduce the value of a skim by shortening credential validity and rotating issued cards, though this only limits window of exposure and does not stop copies made during validity. Refer to CERT/CC VU#676317 at https://kb.cert.org/vuls/id/676317 for coordination updates, and note that any organisational response should also cover the physical security and maritime regulatory implications of a door credential that can be duplicated with a consumer smartphone.

Affected VersionsENISA

door access control N/A

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected technology is NFC-based physical access control built on NXP NTAG212 tags, part of the NTAG21x family of ISO/IEC 14443-A Type 2 compliant tags. The reported flaw maps to CWE-287 (Improper Authentication): the door controller treats an identifier as a verifier. A UID is a 7-byte manufacturer-assigned serial number used by the reader during the ISO 14443-3 anticollision and selection sequence; it is broadcast in cleartext on every tap and is explicitly not a secret, nor is it bound to a cryptographic key. NTAG212 supports password-protected memory and lock bits, but not a mutual-authentication or challenge-response protocol such as those in MIFARE DESFire EV2/EV3 or Seos, so nothing about the card resists duplication. An attacker with any NFC-capable handset or a Proxmark-class tool can capture the UID from a legitimate credential and encode it into a writable tag that the reader will accept as valid, because the reader performs one-way identification (does this serial appear on the allow-list?) instead of authentication (can this card prove possession of a shared secret?). The CPE entry cpe:2.3:a:norwegian_cruise_line:door_access_control:* identifies the deployed access-control implementation as the affected product, with CERT/CC coordinating as case VU#676317 and ENISA tracking it as EUVD-2026-86156. The vulnerability class is architectural: it cannot be remediated by card serial-number rotation, since UIDs are immutable and every read leaks them.

Know when Door Access Control gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (certcc) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 6.1 MEDIUM

NFC skim plus physical presentation at the door makes AV:P; the UID is trivially cloned (AC:L, PR:N, no interaction), and unauthorized entry breaches both access confidentiality and integrity.

3.1 AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
4.0 AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (certcc).

CVSS VectorVendor: certcc

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

2
CVE Published
Sep 24, 2026 - 15:56 cve.org
HIGH 7.5
CVE Published
Sep 24, 2026 - 15:56 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

The NTAG212 NFC door readers protecting cabin, crew, and restricted-area doors across the Norwegian Cruise Line fleet can be opened by anyone who captures a credential's static serial number at close range, because the reader trusts that number alone with no cryptographic challenge. No vendor patch has been identified, and the flaw is intrinsic to the deployed reader/credential scheme, so it applies to every credential and reader pair in service rather than to isolated units. Leadership should care because this is a fleet-wide physical security exposure affecting guest and crew safety, asset protection, and brand trust, and it cannot be closed by configuration alone.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: disable UID-only authentication on affected readers where configuration permits and require a PIN or secondary factor at high-value doors; increase staffed monitoring and camera coverage at guest, crew, and restricted-area entry points; require photo or keyed verification for access to sensitive spaces such as the bridge, engine rooms, and storage; audit and monitor door access logs for anomalous or repeated entry patterns; issue RFID-blocking sleeves to protect credentials from close-range skimming; and accelerate replacement of NTAG212 credentials with challenge-response credentials such as MIFARE DESFire EV3 or NTAG 424 DNA.

Threat Intelligence Overview

EPSS Score
0.4%
Top 73% exploitable
Prevalence
Rare
single-operator proprietary shipboard access system, no broad deployment footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy