Authorization Bypass via Inconsistent Trailing-Slash Handling

In Eclipse BaSyx Go Components versions up to and including 1.0.0, ABAC-enabled deployments are vulnerable to an authorization bypass caused by inconsistent trailing-slash handling between the ABAC middleware and the HTTP router. The shared router configuration used Chi's `middleware.StripSlashes`, so a request such as `GET /shells/` was dispatched to the registered `GET /shells` route. However, the ABAC middleware evaluated the original request path including the trailing slash. If ABAC route lookup did not find a matching slash-suffixed route, the request was passed onward and the router then stripped the slash and executed the protected handler without the intended ABAC authorization decision and without the expected ABAC query filters. An unauthenticated or unauthorized network attacker could append a trailing slash to protected API routes to reach handlers that should have been denied by ABAC policy. Depending on the exposed component, HTTP method, and deployed policy, this

Casky was already ahead

This CVE exploits attack patterns that Casky's 283matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

CVE-2026-15704 exploits a path normalization mismatch in Eclipse BaSyx Go Components, where the HTTP router strips trailing slashes before routing, but the ABAC (Attribute-Based Access Control) middleware evaluates the original unmodified path. This means an attacker can bypass access controls by appending a trailing slash to a protected endpoint—the router normalizes it to match a registered route, but the ABAC policy may not recognize it as the same resource. Organizations deploying BaSyx for industrial control systems, digital twins, and asset administration shells are at critical risk, as this vulnerability allows unauthenticated or low-privileged users to access restricted operations and sensitive data.

Casky's 283 mapped skills leverage Claude's extended reasoning to identify the attack surface across MITRE ATT&CK techniques TA0004 (Privilege Escalation) and TA0006 (Credential Access). Practitioners using Casky would detect this pattern through findings that reveal inconsistent authorization decisions on semantically identical endpoints, policy logic flaws that fail to normalize paths before evaluation, and HTTP requests with and without trailing slashes returning different access-control outcomes. The platform's skills would flag the root cause—CWE-180 (Incorrect Behavior Order) combined with CWE-284 (Improper Access Control)—enabling teams to prioritize remediating ABAC middleware path normalization logic before threat actors exploit these authorization gaps in production deployments.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

283 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-15704.

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

Access with Stolen Session Cookie

identity access management · low

Run

MITRE ATT&CK Techniques

TA0004 TA0006

Investigate the attack patterns behind CVE-2026-15704

Casky has 283 skills that investigate the attack patterns behind CVE-2026-15704. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn