CVE-2026-8725
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 weakness has been identified in CoreWorxLab CAAL up to 1.6.0. The affected element is an unknown function of the file src/caal/webhooks.py of the component test-hass Endpoint. This manipulation causes server-side request forgery. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks. 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 confidenceServer-Side Request Forgery (SSRF) vulnerability in the test-hass endpoint of CoreWorxLab CAAL (versions up to 1.6.0) in src/caal/webhooks.py. The endpoint allows an attacker to make the server perform requests to arbitrary URLs, potentially accessing internal services or bypassing network restrictions.
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.
-
Locate the webhooks.py fileSearch for the file src/caal/webhooks.py in your CoreWorxLab CAAL installation directory. This is the file containing the vulnerable test-hass endpoint.Affected if The file exists and contains a test-hass or similar endpoint handler that processes URL parameters.
-
Identify the installed versionCheck the version of CoreWorxLab CAAL installed in your environment. Look in your package configuration, setup.py, pyproject.toml, or version file. Compare it against the affected range: versions up to and including 1.6.0.Affected if The installed version is 1.6.0 or any earlier version.
-
Inspect the endpoint implementationOpen src/caal/webhooks.py and locate the test-hass endpoint function. Examine how it handles URL parameters and whether it makes HTTP requests based on user input.Affected if The endpoint accepts a URL parameter and passes it to an HTTP request function without strict validation.
-
Check endpoint accessibilityDetermine if the test-hass endpoint is exposed. Check your web server routing configuration, URL routes, or API documentation to see if this endpoint is accessible via HTTP/HTTPS.Affected if The endpoint is exposed and accepts external requests.
-
Verify URL validation is absent or weakReview the code in webhooks.py around the test-hass endpoint. Look for URL validation logic such as allowlists, domain restrictions, or sanitization functions before making HTTP calls.Affected if No URL validation, an incomplete allowlist, or weak validation exists before the server makes outbound requests.
You are affected if CoreWorxLab CAAL version 1.6.0 or earlier is installed, the webhooks.py file exists with the test-hass endpoint, and that endpoint accepts URL parameters without strict validation.
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 strict URL allowlist validation and input sanitization for the webhooks endpoint. Restrict outbound requests to trusted domains and validate all URL parameters server-side before making HTTP requests.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8725 — 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-8725 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