CVE-2026-8725: CoreWorxLab CAAL SSRF
High CVSS (7.3) vulnerability; prioritize internet-facing assets.
TL;DR - CVE-2026-8725 is a high-severity server-side request forgery (SSRF) vulnerability affecting CoreWorxLab CAAL through version 1.6.0. - NVD reports that public exploit code is available, but active exploitation has not been confirmed. - No verified fixed version was identified. Restrict or disable
test-hass, enforce outbound filtering, and block cloud metadata access.
Vulnerability at a Glance
| Field | Details |
|---|---|
| CVE ID | CVE-2026-8725 |
| Product | CoreWorxLab CAAL |
| Affected versions | 1.6.0 and earlier |
| Vulnerability | Server-side request forgery (SSRF) |
| CVSS | 7.3, High |
| Attack vector | Network / remote exploitation |
| Authentication required | Not specified in the retrieved NVD data |
| Privileges required | Not specified in the retrieved NVD data |
| Affected component | test-hass endpoint |
| Source location | src/caal/webhooks.py |
| Patch available | No verified fixed version identified |
| Public PoC or exploit | Yes, according to NVD |
| Confirmed exploitation in the wild | Not established |
| CISA KEV status | Not listed |
CVE-2026-8725 affects CoreWorxLab CAAL installations running version 1.6.0 or any earlier release. The vulnerable functionality is associated with the test-hass endpoint and an unspecified function in src/caal/webhooks.py.
The immediate operational concern is exposure. An SSRF endpoint can make the CAAL server send requests to destinations selected or influenced by an attacker. The impact depends on network placement, outbound firewall rules, endpoint authentication, response handling, and whether the host can reach sensitive internal services.
For background on detection engineering, see our guide to what Sigma is and how to write a detection.
Analyst’s Take: Treat internet-exposed CAAL deployments at or below 1.6.0 as the first priority, especially where
test-hassis reachable without trusted-network restrictions. NVD reports a public exploit, but active exploitation has not been established and the retrieved record does not confirm the exact request behavior. Restricting the endpoint and limiting outbound access are the practical controls available while no verified fixed version has been identified.
What Is This Vulnerability?
The issue is a server-side request forgery vulnerability. In an SSRF attack, an external requester abuses a server-side feature that performs network requests, causing the application to connect to a destination that the attacker could not reach directly. Typical targets include loopback services, private RFC 1918 networks, internal DNS names, link-local services, and cloud instance metadata endpoints.
The NVD description identifies the affected area as the test-hass endpoint in src/caal/webhooks.py, but does not disclose the exact vulnerable function, accepted parameters, HTTP methods, authentication requirements, or response behavior. The available authoritative material therefore does not establish whether the root cause is missing destination validation, unsafe redirect handling, DNS rebinding exposure, inadequate IP-range filtering, or another implementation flaw.
Technical Notes
The vulnerable code location identified in the available record is:
src/caal/webhooks.py
The precise missing control has not been confirmed. Defenders should not assume that blocking only obvious private IP literals is sufficient. If the application follows redirects, resolves hostnames server-side, or accepts alternate address representations, an attacker may attempt to bypass simplistic filters.
Potential SSRF targets that should be considered during exposure review include:
127.0.0.1
localhost
10.0.0.0/8
172.16.0.0/12
192.168.0.0/16
169.254.169.254
::1
fc00::/7
These values are examples of destinations that should be protected by network controls, not confirmed exploit payloads for this CVE.
Who Is Affected?
Organizations are affected if they operate CoreWorxLab CAAL version 1.6.0 or earlier and expose the vulnerable functionality. The identified product and range are:
| Product | Affected range | Component |
|---|---|---|
| CoreWorxLab CAAL | 1.6.0 and earlier | test-hass endpoint |
The NVD record does not provide a more granular range, configuration prerequisite, or statement that every installation exposes the endpoint. Treat all CAAL deployments at or below 1.6.0 as potentially vulnerable until the endpoint is disabled, access is restricted, or a verified security fix is available.
Risk is highest when CAAL is internet-accessible, when unauthenticated users can reach test-hass, or when the CAAL host has broad access to internal systems. Cloud-hosted deployments require particular attention because a successful SSRF may permit requests toward link-local metadata services, although the available sources do not confirm that metadata access has been demonstrated for this CVE.
CVSS Score Breakdown
CVE-2026-8725 has a reported CVSS v3 base score of 7.3, which corresponds to a High severity rating. The retrieved NVD result did not return the complete CVSS vector, so the individual metric values cannot be stated reliably.
The available assessment does establish that the vulnerability is remotely exploitable. However, the record does not specify whether authentication is required, whether privileges are needed, whether user interaction is involved, or how confidentiality, integrity, and availability impacts were calculated. Those unknowns matter when prioritizing the vulnerability across different deployments.
| CVSS element | Available information |
|---|---|
| Base score | 7.3 |
| Severity | High |
| Vector string | Not returned in the retrieved NVD result |
| Network reachability | Remote exploitation reported |
| Authentication | Not specified |
| Privileges required | Not specified |
| User interaction | Not specified |
| Confidentiality impact | Not specified |
| Integrity impact | Not specified |
| Availability impact | Not specified |
Do not attempt to reverse-engineer the missing vector from the score alone. For practical prioritization, combine the High rating with internet exposure, endpoint authentication, outbound network reachability, and the availability of a public exploit reference.
Exploitation Status
NVD states that an exploit has been made publicly available. The NVD-listed GitHub reference is a public issue in the juruo123/public_exp repository:
https://github.com/juruo123/public_exp/issues/5
The retrieved GitHub response did not expose enough issue-body content to independently extract or validate exploit steps and payloads. The existence of the public reference is supported by the NVD record, but defenders should review the issue directly and validate any testing procedure in an authorized, isolated environment.
Confirmed active exploitation in the wild has not been established from the available sources. The CVE is also not listed in the CISA Known Exploited Vulnerabilities catalog. That status does not make the issue low risk: public exploit availability can enable opportunistic scanning, especially against internet-facing endpoints.
| Evidence category | Status |
|---|---|
| Public exploit or PoC reference | Yes, according to NVD |
| Confirmed in-the-wild exploitation | Not established |
| CISA KEV listing | No |
| Confirmed ransomware use | No KEV evidence identified |
How to Detect It
Detection should focus on requests reaching the test-hass endpoint and outbound connections made by the CAAL process. Review reverse-proxy, web-server, application, DNS, firewall, and cloud-flow logs. Look for unexpected requests to loopback, private, link-local, or internal destinations, particularly when the source process is the CAAL service.
Because the exact request parameter and HTTP behavior are not documented in the retrieved sources, a generic endpoint-focused search is more defensible than a presumed payload signature. Establish normal test-hass usage first, then alert on unusual source addresses, request frequency, destination classes, and outbound response sizes.
Technical Notes
A generic reverse-proxy search might begin with:
grep -RniE '(^|[[:space:]/])test-hass([/?[:space:]]|$)' \
/var/log/nginx /var/log/apache2 2>/dev/null
For JSON or structured HTTP logs, an example jq query is:
jq -r '
select(
(.request_uri // .url // "") | test("/test-hass")
)
| [
(.timestamp // .["@timestamp"] // "-"),
(.remote_addr // .client_ip // "-"),
(.request_uri // .url // "-"),
(.status // .response_status // "-")
]
| @tsv
' /var/log/caal/access.json
The following Sigma-style logic is a starting point, not a confirmed CVE signature:
title: Possible CAAL SSRF Targeting Internal Destinations
logsource:
category: proxy
detection:
endpoint:
url|contains: "/test-hass"
destination:
url|contains:
- "127.0.0.1"
- "localhost"
- "169.254.169.254"
- "10."
- "172.16."
- "172.17."
- "172.18."
- "172.19."
- "172.20."
- "172.21."
- "172.22."
- "172.23."
- "172.24."
- "172.25."
- "172.26."
- "172.27."
- "172.28."
- "172.29."
- "172.30."
- "172.31."
- "192.168."
condition: endpoint and destination
level: high
At the network layer, alert when the CAAL host initiates connections to destinations it does not normally contact, including TCP connections to 169.254.169.254, loopback-adjacent services, internal administrative ports, or unexpected private address ranges. Exact firewall fields vary by platform, so the source identity should be tied to the CAAL host, container, pod, or service account.
Mitigation and Patching
No verified fixed version was identified in the available sources. The affected range remains CAAL 1.6.0 and earlier, and the vendor reportedly did not respond to the disclosure. Do not describe an upgrade as complete remediation unless the project publishes a release or commit that explicitly fixes this SSRF and the change has been reviewed.
The preferred interim control is to disable the test-hass endpoint if it is not required. If it is required, restrict it to trusted administrative networks or authenticated management clients, place it behind a reverse proxy with strict access control, and limit the CAAL host’s outbound network access. These controls reduce exposure but do not repair the underlying application flaw.
Technical Notes
There is no confirmed fixed version, so no authoritative package upgrade command can be provided. Before upgrading, verify the project’s release information and inspect the deployed version:
python -m pip show caal
python -m pip index versions caal
If CAAL is deployed from a Git checkout, record the current revision before applying a reviewed security change:
git -C /opt/caal rev-parse HEAD
git -C /opt/caal remote -v
Only after confirming an authoritative release or commit that addresses CVE-2026-8725 should an organization use an upgrade procedure such as:
python -m pip install --upgrade 'caal==<verified-fixed-version>'
The placeholder must be replaced with a version confirmed by project documentation or source review. It is intentionally not populated because no fixed version was identified.
A temporary reverse-proxy restriction can be implemented with an allowlist. For example, in Nginx:
location = /test-hass {
allow 10.0.0.0/8;
allow 192.168.0.0/16;
deny all;
proxy_pass http://caal_backend;
}
This example must be adapted to the organization’s trusted management ranges. It is not a substitute for disabling the endpoint or fixing the application. Also enforce egress controls at the host, container, security-group, or firewall layer. At minimum, block the CAAL runtime from reaching cloud metadata services unless there is a documented business requirement:
Deny outbound TCP from CAAL host to 169.254.169.254:80
Deny outbound access from CAAL host to unapproved private network ranges
Allow outbound connections only to documented integration destinations
After applying controls, test that legitimate CAAL integrations continue to function and that requests to internal, loopback, link-local, and metadata destinations are rejected before reaching sensitive services.
References
The primary vulnerability record is the NVD entry for CVE-2026-8725:
NVD lists the following public disclosure or exploit reference:
Additional vulnerability database references include:
CISA’s Known Exploited Vulnerabilities catalog should be checked during reassessment:
At the time of this assessment, CVE-2026-8725 was not listed in CISA KEV, and no verified patched CAAL release was identified. Organizations should monitor the project repository and release channels for a security advisory or fixed version while maintaining endpoint restrictions and egress controls.
This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.