Skip to main content
CVE-2025-49004VulnerabilityPublished

CVE-2025-49004: caido · Authentication Bypass by Spoofing

Affects caidoSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 0.48.0 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.48.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jun 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-26.

What to do

Upgrade caido/caido to 0.48.0.

Affected software

ProductAffectedFixed in
GitHubcaido/caidopkg:github/caido/caidoOther threatsAffected
  • <0.48.0
Fixed in
  • 0.48.0

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

AI-suggested

1. Immediate upgrade to Caido version 0.48.0 or later, which includes patches for DNS rebinding protections. 2. Implement network-level protections to restrict access to local Caido instances, such as firewall rules or local host binding to prevent external access. 3. Educate users and security teams about the risks of visiting untrusted websites while running local security tools. 4. Employ browser security features or extensions that mitigate DNS rebinding attacks, such as enforcing strict origin policies or disabling DNS rebinding where possible. 5. Monitor network traffic and logs for suspicious DNS rebinding patterns or unauthorized access attempts to local services. 6. For organizations deploying Caido in shared or multi-user environments, enforce strict authentication and session management controls to reduce the risk of hijacking. 7. Conduct regular security audits of internal tools to ensure they are up to date and configured securely, including validation of origin headers and use of anti-rebinding techniques like checking the Host header or implementing token-based authentication flows. 8. Consider isolating security auditing tools in sandboxed or virtualized environments to limit the impact of potential compromises.

Description

Caido is a web security auditing toolkit. Prior to version 0.48.0, due to the lack of protection for DNS rebinding, Caido can be loaded on an attacker-controlled domain. This allows a malicious website to hijack the authentication flow of Caido and achieve code execution. A malicious website loaded in the browser can hijack the locally running Caido instance and achieve remote command execution during the initial setup. Even if the Caido instance is already configured, an attacker can initiate the authentication flow by performing DNS rebinding. In this case, the victim needs to authorize the request on dashboard.caido.io. Users should upgrade to version 0.48.0 to receive a patch.

References

Community reviews

Loading reviews…