Skip to content
Applications

CVE-2026-15704

9.8
Critical
EPSS 0.37%Patch availableJul 24, 2026

AuthZ bypass via trailing-slash mismatch in Eclipse BaSyx Go Components

common questions

Is CVE-2026-15704 being exploited?

Not confirmed. CVE-2026-15704 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.

How severe is CVE-2026-15704?

CVE-2026-15704 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-15704?

Yes. A fix has been recorded for CVE-2026-15704. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-15704 affect?

CVE-2026-15704 affects Eclipse BaSyx Go Components <=1.0.0, AAS Repository, Submodel Repository, AAS Registry, and 4 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-15704?

Upgrade to Eclipse BaSyx Go Components v1.0.1 and audit ABAC route handling/logs

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Eclipse BaSyx Go Components <=1.0.0AAS RepositorySubmodel RepositoryAAS RegistrySubmodel RegistryConcept Description RepositoryDiscoveryAAS Environment upload
impact

Authorization bypass: attackers can append a trailing slash to access protected AAS endpoints and perform unauthorized read/create/update/delete/upload.

action required

Immediate action required

affected versions
Eclipse Foundation Eclipse BaSyx Go Components
  • affected< 1.0.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free