Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain physical access to device
-
DeliveryInteract with QNAP Authenticator app
-
ExploitExploit improper authentication (CWE-287)
-
ExecutionBypass authentication controls
-
ImpactCompromise protected credentials/tokens
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 access (AV:P) to a device running QNAP Authenticator at version 1.3.x below 1.3.1.1227, plus passive user interaction (UI:P) - the attacker cannot act purely remotely or fully autonomously. No authentication is needed on the attacker's part (PR:N), but the device must be physically reachable, which is the dominant limiting factor: the flaw is not remotely exploitable, cannot be automated at scale, and is confined to the QNAP Authenticator mobile/companion app rather than the NAS itself. The vendor description names no special configuration toggle; the governing precondition is simply possession of a vulnerable-version device. |
| Impact | Real-world risk is LOW-to-MODERATE despite the 6.9 (Medium) CVSS 4.0 score, and the signals are mutually consistent rather than conflicting. The vendor-supplied CVSS 4.0 vector (AV:P/AC:L/AT:N/PR:N/UI:P) makes the single most important limiter explicit: AV:P means exploitation requires physical access to the device running QNAP Authenticator, which collapses this from a scalable remote threat to an opportunistic, per-device attack. This is strongly corroborated by the EPSS score of 0.06% (20th percentile), which places it well below the threshold predictive of volume exploitation - exactly what one expects for a physical-access bug that cannot be sprayed across the internet. The CVE is NOT on the CISA KEV catalog and no proof-of-concept is referenced, so there is no evidence of active or public exploitation. High confidentiality and integrity impact (VC:H/VI:H) is the one factor that raises stakes: a successful attacker defeats the authentication protection the app is meant to provide. Net assessment: this is a legitimately patch-worthy flaw for high-value or shared-device scenarios, but it is a low operational priority for most fleets compared with network-exploitable issues - it is a defensible-in-depth fix, not an emergency. |
| Exploit ScenarioDerived | An attacker who obtains temporary physical possession of an unlocked or targeted device running an unpatched QNAP Authenticator (e.g., a lost, stolen, or briefly unattended phone) manipulates the app to bypass its authentication protection, requiring some passive user interaction (UI:P). This defeats the second factor the app exists to protect, potentially exposing or forging the credentials/tokens it guards (VC:H/VI:H). No public exploit code or active exploitation has been identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 18, 2026
Improper authentication in QNAP Authenticator 1.3.x before 1.3.1.1227 lets an unauthenticated attacker who gains physical access to the device running the mobile/companion app subvert authentication and compromise the security of the authenticator installation. The flaw is not remotely exploitable, requires passive user interaction, and is assessed as low-to-moderate real-world risk despite a 6.9 Medium CVSS 4.0 score; EPSS is 0.06% (20th percentile), and no public exploit or CISA KEV entry is identified. QNAP has released a fixed build, 1.3.1.1227 and later.
Earlier versions of this analysis (1)
RemediationAI
Upgrade QNAP Authenticator to 1.3.1.1227 or later, which is the vendor-released patch for this issue, and follow QNAP advisory QSA-25-30 at https://www.qnap.com/en/security-advisory/qsa-25-30. Until all devices are updated, restrict physical access to phones or devices running QNAP Authenticator, enforce device passcode/biometric lock and app-level lock, use MDM enrollment with remote wipe for lost or stolen devices, and monitor for unauthorized device possession; these controls reduce exposure but do not eliminate the flaw, and stricter device lockout or MDM policies can add user-support and availability overhead. No public exploit was identified at time of analysis, so remediation should prioritize the vendor update and physical-access controls rather than emergency network mitigations.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The issue is classified as CWE-287 (Improper Authentication) in QNAP Authenticator, the companion/mobile authenticator app, rather than in NAS firmware. The CPE cpe:2.3:a:qnap:authenticator:*:*:*:*:*:*:*:* is a wildcard, and EUVD narrows the affected range to QNAP Authenticator 1.3.x below 1.3.1.1227. The CVSS 4.0 vector AV:P/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N shows that the dominant precondition is physical access (AV:P), with no attacker authentication required (PR:N) but passive user interaction (UI:P); the independent CVSS 3.1 assessment is AV:P/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L. In practical terms, the governing condition is possession of a vulnerable-version device, which limits exploitation to local, non-scalable scenarios rather than remote attacks.
Know when Authenticator 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
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
Physical access drives AV:P; no attacker privileges needed (PR:N) but victim interaction is required (UI:R); authentication bypass yields high confidentiality and integrity impact with limited availability effect.
Primary rating from Vendor (qnapsecurity).
CVSS VectorVendor: qnapsecurity
Lifecycle Timeline
3DescriptionCVE.org
An improper authentication vulnerability has been reported to affect QNAP Authenticator. If an attacker gains physical access, they can then exploit the vulnerability to compromise the security of the system.
We have already fixed the vulnerability in the following version: QNAP Authenticator 1.3.1.1227 and later
Executive ViewAI
Organizations using An improper authentication vulnerability should be aware of notable risk from CVE-2025-54154, a improper authentication vulnerability rated CVSS 6.8. This could allow unauthorized access to protected resources. Organizations should apply vendor updates when available and monitor for exploitation.
Apply vendor patch. If patching is delayed: restrict network access, enable MFA, monitor auth logs.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Authenticator
View allLocal privilege escalation in Microsoft Authenticator for Android (versions 6.0.0 through below 16.3.0) allows a local a
Authenticator is a browser extension that generates two-step verification codes. Rated high severity (CVSS 7.8), this vu
Under certain conditions SAP Authenticator for Android allows an attacker to access information which would otherwise be
Microsoft Authenticator Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.1), this vulnerability is no a
SAP Authenticator for Android - version 1.3.0, allows the screen to be captured, if an authorized attacker installs a ma
pam_google_authenticator.c in the PAM module in Google Authenticator before 1.0 requires user-readable permissions for t
Microsoft Authenticator contains an information disclosure vulnerability that allows local attackers to access sensitive
EUVD-2025-32454
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB