Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessPosition within router wireless range
-
DeliveryObserve admin IFTTT pairing session values
-
ExploitDerive pairing token from predictable PRNG seed
-
ExecutionAuthenticate to router with forged token
-
ImpactRead or modify router settings
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Unpredictable PRNG seeds
|
| Exploitation Conditions | Exploitation requires that the IFTTT integration feature be in use and that an administrator actively initiate an IFTTT pairing session while the attacker is present; the attacker must be within adjacent (wireless/radio) range of the ASUS RT-BE57 and able to observe the values emitted during that pairing exchange to reconstruct the token from the predictable PRNG seed. Limiting factors: adjacency is mandatory (not internet-reachable, AV:A), the attack is high-complexity (AC:H) and carries a present attack requirement (AT:P) because it depends on capturing a transient, admin-triggered pairing session - routers where IFTTT pairing is never used are not exploitable. No attacker authentication or victim click is required (PR:N/UI:N), but the dependence on a live pairing event makes exploitation opportunistic rather than on-demand. |
| Impact | The CVSS 4.0 base score of 7.7 (High) is driven by full high impact to confidentiality, integrity and availability of the router (VC:H/VI:H/VA:H), but tempered by significant exploitation barriers: adjacent-network vector (AV:A), high attack complexity (AC:H), and a present attack requirement (AT:P) - the attacker must observe a live administrator-initiated IFTTT pairing session to derive the predictable PRNG seed (CWE-337). PR:N/UI:N means no attacker privileges or victim interaction are needed, but the AT:P/AC:H combination means success hinges on an attacker being within wireless range at the exact moment an admin performs IFTTT pairing - a narrow, opportunistic window rather than a mass-exploitable condition. No EPSS score, KEV listing, or POC is present in the supplied data, so there is no public exploit identified at time of analysis and no evidence of active exploitation; this reads as a credible but conditional, targeted-only risk rather than a widespread emergency. The signals are internally consistent (adjacency + session observation + no auth all align), so no contradictions require vendor verification, though the exact affected firmware versions are not enumerated in the input. |
| Exploit ScenarioDerived | An attacker within wireless range of an ASUS RT-BE57 router passively observes the values exchanged during an administrator-initiated IFTTT pairing session. Because the pairing token is generated from a predictable PRNG seed, the attacker reconstructs the token from the observed values and then uses it to read and modify router settings. No public exploit code is identified at time of analysis, and success requires catching a pairing session in progress. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Derivation of IFTTT pairing tokens in the ASUS RT-BE57 router allows an unauthenticated attacker within adjacent wireless range to read or modify router settings, provided they can observe a live administrator-initiated IFTTT pairing exchange. The root cause is a predictable seed in the pairing-token PRNG (CWE-337), which lets the attacker reconstruct the token from values emitted during that session; the assessed CVSS 3.1 vector (AV:A/AC:H/PR:N/UI:N, C:H/I:H/A:H) reflects full impact to router confidentiality, integrity, and availability but heavily conditioned on adjacency, high attack complexity, and a present attack requirement. Exploitation is therefore opportunistic rather than on-demand and only affects deployments where IFTTT integration is actually used; no public exploit code has been identified at time of analysis.
RemediationAI
Apply the current ASUS router firmware from the 'Security Update for ASUS Router Firmware' section of the vendor advisory at https://www.asus.com/security-advisory; patch availability is confirmed per vendor advisory, but an exact fixed firmware version is not specified in the provided data, so administrators should treat 'latest available for the RT-BE57' as the target and verify the release notes for the IFTTT pairing fix. Because the attack hinges on an admin-initiated pairing session, the most effective interim control is to disable or avoid the IFTTT cloud integration on the RT-BE57 until firmware is updated - the trade-off is loss of IFTTT automation functionality, and any already-issued pairing token should be revoked or the pairing re-established only after patching. Restrict the exposure window by performing pairing only when no untrusted clients are within wireless range and by never initiating pairing from an untrusted location, since that condition is what makes token reconstruction possible. Additional hardening with modest trade-offs includes enforcing WPA3/strong PSKs and disabling WPS to reduce the pool of nearby unauthenticated observers, placing the router's management interface on a segregated VLAN with strict admin-password policy and remote administration disabled, and monitoring router logs for anomalous configuration changes or unexpected pairing requests. Each of these reduces attack opportunity but none removes the predictable-PRNG root cause, so firmware update remains the definitive fix.
Affected VersionsENISA
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 flaw is a class CWE-337 weakness - predictable seed in a pseudo-random number generator - inside the IFTTT (If This Then That) cloud-integration pairing flow of the ASUS RT-BE57. To bind a router to an IFTTT account, the device generates a pairing token from a PRNG whose initial seed is insufficiently random; an attacker who passively observes the values exchanged during an admin-triggered pairing session can reproduce the seed and derive the corresponding token. Because the token authorizes actions on the router's configuration surface, possession of it yields read and write access to settings without any credential or user interaction (PR:N/UI:N). The CVSS 4.0 vector highlights the constraints precisely: AV:A (adjacent - the attacker must be within wireless/radio range, not internet-reachable), AC:H (the derivation depends on a transient, admin-initiated session), and AT:P (a present attack requirement, i.e. the vulnerable pairing exchange must be occurring at the moment of observation). Impact metrics VC:H/VI:H/VA:H confirm loss of confidentiality, integrity, and availability of the device, while subsequent-system metrics are all N, so the blast radius is the router itself rather than downstream networks. The provided CPE cpe:2.3:a:asus:router:*:*:*:*:*:*:*:* is a family-level wildcard, so the exact firmware builds carrying the vulnerable pairing implementation are not enumerated in the available data.
Know when Router 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:A/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Adjacent wireless range gives AV:A; dependence on observing a transient admin pairing session makes AC:H; no attacker auth gives PR:N; full read/modify of router settings yields C:H/I:H/A:H with unchanged scope.
Primary rating from Vendor (ASUS).
CVSS VectorVendor: ASUS
DescriptionCVE.org
A predictable seed in the pseudo-random number generator (PRNG) in the IFTTT pairing token generation of the ASUS RT-BE57 router allows an unauthenticated nearby user to derive the pairing token and read or modify router settings via observed values from an administrator-initiated IFTTT pairing session.Refer to the ' Security Update for ASUS Router Firmware ' section on the ASUS Security Advisory for more information.
Executive ViewAI
The ASUS RT-BE57 router is affected by a high-severity vulnerability (CVE-2026-19396) that, when IFTTT integration is enabled, could allow an unauthenticated attacker within wireless range to alter router settings. No public exploit has been identified at time of analysis, but no vendor-released patch is identified at time of analysis, leaving organizations that rely on this router exposed to potential network disruption or unauthorized configuration changes. Leadership should assess their exposure and prioritize interim mitigations, especially where IFTTT is actively used.
Disable IFTTT integration; restrict physical and wireless access to the router; implement network segmentation to limit lateral movement; enable logging and monitoring for IFTTT pairing events; use strong wireless encryption (WPA2/WPA3) and consider MAC address filtering to reduce adjacency risk.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Related Vulnerabilities in ASUS Router Code Execution and Info Disclosure
View all 4Unauthenticated remote attackers can enable Telnet on TOTOLINK X5000R AX1800 routers running firmware V9.1.0u.6369_B2023
Depending on the configuration of the route permission table in file 'saprouttab', it is possible for an unauthenticated
OS command injection in Netcore NAP930 firmware 0.1.241010.141410 allows unauthenticated remote attackers to execute arb
An unauthenticated OS command injection in the CGI handler of Netcore NR289-GE firmware 1.4.5102 lets remote attackers e
Missing authorization in Netcore NBR100V2 firmware 1.3.240614.030928 allows remote unauthenticated attackers to modify d
Authenticated administrators of ASUS routers can execute arbitrary commands on the device by uploading a crafted file th
Unauthenticated network attackers can bypass authentication in the Netcore NR289-GE router's boa_temp web handler and ab
Remote unauthenticated OS command injection in Netcore NR289-GE firmware 1.4.5102 allows attackers to execute arbitrary
Unauthenticated OS command injection in the Netcore NR289-GE router (firmware 1.4.5102) lets any remote attacker who can
A stack-based buffer overflow in the devdiscover service of FAST FAC1900R firmware 20190827_2.0.2 lets unauthenticated r
Unauthenticated OS command injection in the Netcore NBR200V2 router's Web Management Interface (firmware 1.3.241127.0712
Authenticated administrators of certain ASUS router models can abuse leftover debug code in the device's web management
EUVD-2026-94158
GHSA-fcpg-rqrm-22xm
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB