Predictable PRNG seed exposes pairing tokens and settings in ASUS RT-BE57 Router

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-19396?

CVE-2026-19396 is a vulnerability classified as Predictable Seed in Pseudo-Random Number Generator (PRNG), affecting Router (affected versions: 3.0.0.6_102 series). This vulnerability is rated High, with a CVSS score of 7.7. Current sources do not report this vulnerability as exploited.

Overview

Original source data

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.

Affected products and scope

ASUS Router, with the vulnerability description identifying the ASUS RT-BE57 Router:

  • 3.0.0.6_102 series: explicitly marked affected.
  • The record's default status is unaffected for products or versions not covered by the affected entry.
  • No fixed release or safe version boundary is supplied. Other versions and parallel release branches must not be assumed to be fixed.

Technical details

The flaw is in the ASUS RT-BE57 Router IFTTT pairing-token generation flow, where the seed used by the pseudo-random number generator (PRNG) is predictable. An unauthenticated nearby user can observe values from an administrator-initiated IFTTT pairing session and use them to derive the pairing token. The derived token may then allow the attacker to read or modify router settings. The required condition is an observable administrator-initiated pairing session; the available evidence does not specify the seed source, the number of values required, the token format, or the endpoints that process the token.

Exploitability

The vulnerability is reachable from an adjacent network position by an unauthenticated user and does not require direct user interaction with the attacker. The attacker must be able to observe values from an administrator-initiated IFTTT pairing session. Current enrichment records exploitation as none and automatable as no, and the supplied record does not identify a public exploit. This does not establish that exploitation is impossible or that abuse has not occurred outside the available evidence.

Technical impact

An attacker in the vicinity may derive an IFTTT pairing token from values observed during an administrator-initiated pairing session. This may enable reading and modification of router settings, creating risks to configuration confidentiality and integrity and potentially to network service availability. The vulnerability requires no prior privileges and no direct user interaction, but the documented conditions include an observable pairing session and high attack complexity. The available evidence does not establish which administrative operations are exposed, how long access remains valid, or whether systems behind the router can be reached.

Business impact

If the attacker can observe the required pairing session, the attacker may gain access to router settings without valid credentials. Consequences can include exposure of configuration information, unauthorized changes to network or service parameters, and service disruption if modified settings affect connectivity or router operation. The practical scope depends on which settings the pairing token authorizes. The record does not confirm a breach, victim, campaign, or specific configuration change.

Remediation

  1. Review the Security Update for ASUS Router Firmware section of the ASUS Security Advisory for firmware guidance applicable to the RT-BE57 Router.
  2. If ASUS provides a vendor-confirmed corrective firmware release, deploy that release after appropriate testing and change control. The current record does not name a fixed version.
  3. Until the corrective release is identified, avoid or defer IFTTT pairing sessions in environments where an untrusted nearby user could observe the exchange. This is a precaution based on the documented attack condition, not a vendor-confirmed patch.
  4. After updating, verify the model and firmware version on every device and review settings associated with earlier pairing sessions.

Detection

  1. Inventory ASUS RT-BE57 Router devices and record the firmware version running on each device.
  2. Compare installed versions with the affected 3.0.0.6_102 series branch.
  3. Review administrator-initiated IFTTT pairing sessions, especially sessions conducted where an untrusted nearby user could observe the exchange.
  4. Check for unexpected router-setting changes following those pairing sessions.
  5. No specific IOC, log event, or telemetry pattern is provided by the available sources. Monitoring pairing activity and configuration changes is a precautionary measure, not a confirmed indicator.
Sources (13)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.