Skip to main content
VulnerabilityPublished

CVE-2025-46658: Generation of Error Message Containing Sensitive Information

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% 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:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Aug 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 26 Oct 2026.

What to do

AI-suggested

Organizations should immediately review and harden the error handling and logging configurations within their ExonautWeb deployments to suppress verbose error messages from being displayed to end users or logged insecurely. This includes configuring the application to provide generic error messages that do not reveal internal details. Network segmentation and strict access controls should be enforced to limit exposure of the ExonautWeb interface to trusted users only. Monitoring and alerting on unusual application errors or access patterns can help detect exploitation attempts. Since no official patches are available, organizations should engage with 4C Strategies to obtain guidance or updates. Additionally, conducting a thorough security review and penetration testing of the Exonaut environment can identify other weaknesses that may be exploited in conjunction with this vulnerability. Implementing Web Application Firewalls (WAFs) with rules to block suspicious requests targeting error handling paths may provide temporary protection. Finally, educating users and administrators about the risks of information disclosure and secure error handling best practices is recommended.

Description

An issue was discovered in ExonautWeb in 4C Strategies Exonaut 21.6. There are verbose error messages.

References

Community reviews

Loading reviews…