Skip to main content
CVE-2025-62397VulnerabilityPublished

CVE-2025-62397: router · Generation of Error Message Containing Sensitive Information

Affects routerSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Red Hatredhat/routerpkg:rpm/redhat/routerOther threatsAffected
  • =5.0.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-62397, organizations should first verify if they are running the affected router version 5.0.0 and plan to upgrade to a patched version once available. In the absence of an official patch, administrators should implement the following specific measures: 1) Standardize error messages related to course ID validation to ensure consistent responses regardless of input validity, thereby preventing attackers from inferring valid IDs. 2) Employ input validation and sanitization to limit the exposure of internal identifiers in error outputs. 3) Monitor network traffic for unusual patterns indicative of reconnaissance activities targeting course ID parameters, such as repeated invalid ID submissions. 4) Restrict network access to the router management interfaces to trusted IP ranges and use network segmentation to limit exposure. 5) Implement logging and alerting on suspicious activities related to course ID queries. 6) Educate relevant personnel about the risks of information leakage and encourage prompt reporting of anomalies. These targeted actions go beyond generic advice by focusing on error message handling and reconnaissance detection specific to this vulnerability.

Description

The router’s inconsistent response to invalid course IDs allowed attackers to infer which course IDs exist, potentially aiding reconnaissance.

References

Community reviews

Loading reviews…