CVE-2026-6635
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 · uneditedA security vulnerability has been detected in rowboatlabs rowboat up to 0.1.67. This impacts the function tool_call of the file apps/experimental/tools_webhook/app.py of the component tools_webhook. Such manipulation of the argument X-Tools-JWE leads to improper authentication. The attack may be performed from remote. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 · moderate confidenceAuthentication bypass vulnerability in the tools_webhook component of rowboat library (versions up to 0.1.67). The tool_call function improperly validates the X-Tools-JWE header, allowing remote attackers to bypass authentication by manipulating this JWE token argument.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 if rowboat library is installedRun 'pip show rowboat' or check your requirements.txt/pip freeze for the rowboat packageAffected if rowboat version 0.1.67 or lower is installed
-
Confirm the installed version is vulnerableCompare the installed version to the affected range (versions up to and including 0.1.67)Affected if The installed version is 0.1.67 or any earlier version
-
Check if tools_webhook component is in useSearch your codebase for imports or references to tools_webhook, such as 'from rowboat.plugins import tools_webhook' or 'import tools_webhook'Affected if The tools_webhook component is imported or used in your application
-
Identify if X-Tools-JWE header validation is implementedSearch for the tool_call function in your rowboat installation or codebase and inspect how X-Tools-JWE header is handled; look for JWE token parsing, signature verification, expiration checking, or issuer validation logicAffected if The tool_call function processes X-Tools-JWE header without proper validation or verification
-
Check for exposed tools_webhook endpointsReview your web server or API configuration for endpoints that expose the tools_webhook component, particularly routes that accept X-Tools-JWE headerAffected if The tools_webhook component is exposed via an accessible network endpoint
You are affected if you have rowboat library version 0.1.67 or lower and your application uses the tools_webhook component with X-Tools-JWE header authentication.
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.
From vendor dataImplement proper validation and verification of the X-Tools-JWE header token in the tool_call function, including signature verification, expiration checking, and issuer validation. Until a patch is available, disable the tools_webhook component or restrict network access.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6635 — 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-6635 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