CVE-2026-24853
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCaido is a web security auditing toolkit. Prior to 0.55.0, Caido blocks non whitelisted domains to reach out through the 8080 port, and shows Host/IP is not allowed to connect to Caido on all endpoints. But this is bypassable by injecting a X-Forwarded-Host: 127.0.0.1:8080 header. This vulnerability is fixed in 0.55.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCaido before 0.55.0 has an access control bypass where the domain whitelist protecting port 8080 can be circumvented by injecting an X-Forwarded-Host header with 127.0.0.1:8080, allowing attackers to bypass the Host/IP not allowed protection and access internal services through the 8080 port.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.55.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Caido versionCheck the Caido application version through its UI (typically found in Help > About) or by examining the executable/daemon version flag if available from command lineAffected if The installed version is below 0.55.0 (for example, 0.54.0, 0.53.0, etc.)
-
Confirm port 8080 is exposed or accessibleVerify that port 8080 is listening or configured as an accessible port in the Caido instance (check network bindings or service configuration)Affected if Port 8080 is enabled and reachable from untrusted networks or the bypass condition exists
-
Verify whitelist protection is activeInspect Caido's configuration for domain/IP whitelist settings that protect port 8080 accessAffected if A whitelist protecting port 8080 is configured, which can be bypassed via X-Forwarded-Host header injection
-
Test for X-Forwarded-Host bypassSend a request to Caido with an X-Forwarded-Host header set to 127.0.0.1:8080 and observe if internal services on port 8080 become accessible despite whitelist protectionsAffected if The X-Forwarded-Host header with 127.0.0.1:8080 successfully bypasses the whitelist and grants access to port 8080 services
You are affected if running Caido versions below 0.55.0 with port 8080 accessible and the whitelist protection in place, where injection of the X-Forwarded-Host header can bypass access controls.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.55.0
Upgrade to Caido 0.55.0 or later which includes fixed host header validation to prevent the whitelist bypass.
Caido 0.55.0
- 1. Back up your current Caido configuration and any active project data
- 2. Download Caido version 0.55.0 or later from the official Caido releases (github.com/caido/caido)
- 3. Stop the currently running Caido instance
- 4. Install or replace the existing Caido installation with version 0.55.0
- 5. Start the updated Caido instance
- 6. Verify the X-Forwarded-Host header injection no longer bypasses the domain whitelist restriction
- 7. Confirm the endpoint now properly rejects connections with spoofed X-Forwarded-Host headers attempting to bypass the allowlist
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24853 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24853 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data