CVE-2026-24853
Header Injection Bypass in Caido Web Security Toolkit Before
Publication date: 2026-02-13
Last updated on: 2026-02-24
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| caido | caido | to 0.55.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-290 | This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Caido, a web security auditing toolkit, in versions prior to 0.55.0. Caido is designed to block non-whitelisted domains from accessing the service through port 8080 and normally shows a message "Host/IP is not allowed to connect to Caido" on all endpoints when such access is attempted.
However, this protection can be bypassed by injecting a specially crafted HTTP header, specifically the "X-Forwarded-Host: 127.0.0.1:8080" header. This allows an attacker to circumvent the domain whitelist restriction and potentially access Caido through the restricted port.
The vulnerability was fixed in version 0.55.0 of Caido.
How can this vulnerability impact me? :
Exploiting this vulnerability allows an attacker to bypass domain whitelist restrictions and access Caido through port 8080 by injecting a malicious header.
Given the CVSS v3.1 base score of 8.1 with high impact on confidentiality, integrity, and availability, this could lead to serious security consequences such as unauthorized access, data compromise, or disruption of services.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade Caido to version 0.55.0 or later, where the issue with bypassing domain restrictions via the X-Forwarded-Host header is fixed.