dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-7411

CRITICAL · 10.0 CVSS v3.1 Published 2026-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In Eclipse BaSyx Java Server SDK versions prior to 2.0.0-milestone-10, inadequate path normalization in the Submodel HTTP API allows an unauthenticated remote attacker to perform a path traversal attack. By supplying a maliciously crafted fileName parameter during a file upload operation, an attacker can bypass intended storage boundaries and write arbitrary files to any location on the host filesystem accessible by the Java process. This can lead to Remote Code Execution (RCE) and complete system compromise.

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 · high confidence

Eclipse BaSyx Java Server SDK versions before 2.0.0-milestone-10 contain a path traversal vulnerability in the Submodel HTTP API's file upload functionality. Inadequate path normalization allows unauthenticated attackers to manipulate the fileName parameter to write arbitrary files outside the intended storage directory, leading to RCE.

MitigationUpgrade to Eclipse BaSyx Java Server SDK version 2.0.0-milestone-10 or later which implements proper path normalization to block traversal sequences.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Eclipse BaSyx Java Server SDK installation
    Locate the installed BaSyx SDK by checking your application dependencies (Maven pom.xml, Gradle build file, or JAR manifest) for the eclipse-basyx-java-server-sdk version, or check the SDK's built-in version info if exposed via API endpoint
    Affected if Version is present and is below 2.0.0-milestone-10
  2. Verify Submodel HTTP API is exposed
    Check your server configuration or running endpoints to confirm the Submodel API HTTP endpoints are accessible (typically under /submodels or similar path)
    Affected if Submodel HTTP API endpoints are reachable and operational
  3. Confirm file upload feature is enabled
    Inspect the Submodel API configuration to determine if file upload or fileRepository functionality is enabled (check for relevant upload endpoints or storage-related configuration properties)
    Affected if File upload capability is enabled in the Submodel configuration

A user is affected if they are running Eclipse BaSyx Java Server SDK version below 2.0.0-milestone-10 with the Submodel HTTP API and its file upload feature enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Eclipse BaSyx Java Server SDK version 2.0.0-milestone-10 or later which implements proper path normalization to block traversal sequences.

Recommended fix Moderate confidence

2.0.0-milestone-10 or later

  1. 1. Identify the current version of Eclipse BaSyx Java Server SDK in use by checking project dependencies (e.g., pom.xml for Maven projects)
  2. 2. Locate the specific vulnerable component: Submodel HTTP API file upload functionality
  3. 3. Obtain the fixed release: Eclipse BaSyx Java Server SDK version 2.0.0-milestone-10 or later from the official Eclipse distribution
  4. 4. Update the project dependency version in build configuration (e.g., update version in pom.xml or build.gradle)
  5. 5. Rebuild and redeploy the application
  6. 6. Verify the fix by testing that path traversal characters in fileName parameters are properly rejected or sanitized
Caveat milestone releases may contain API changes; review release notes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7411 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7411 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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