CVE-2026-7412
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 · uneditedIn Eclipse BaSyx Java Server SDK versions prior to 2.0.0-milestone-10, the Operation Delegation feature fails to validate the destination URI of delegated requests. An unauthenticated remote attacker can exploit this design flaw to force the BaSyx server to execute blind HTTP POST requests to arbitrary internal or external targets. This allows an attacker to bypass network segmentation and pivot into isolated internal IT/OT infrastructure or target Cloud Metadata services (IMDS).
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 confidenceThe Eclipse BaSyx Java Server SDK contains a Server-Side Request Forgery (SSRF) vulnerability in its Operation Delegation feature. Versions prior to 2.0.0-milestone-10 fail to validate the destination URI before making delegated HTTP POST requests. An unauthenticated attacker can exploit this to force the server to make blind HTTP POST requests to arbitrary internal or external targets, bypassing network segmentation.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
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.
-
Identify Eclipse BaSyx Java Server SDK installationLocate the BaSyx SDK JAR files or dependency declarations (e.g., in pom.xml, build.gradle, or the application's lib directory) and note the version string.Affected if The installed version is older than 2.0.0-milestone-10 or the version cannot be determined.
-
Check if Operation Delegation feature is enabledReview the server configuration files or runtime settings for the Operation Delegation feature. Look for configuration keys related to delegation, such as 'delegation.enabled', 'operation.delegation', or similar settings in the BaSyx configuration.Affected if Operation Delegation is enabled and the SDK version is vulnerable.
-
Inspect the Operation Delegation endpoint configurationExamine the application's exposed endpoints, particularly any delegation or proxy-related routes (often under paths like '/delegate', '/operations/delegate', or similar). Verify if the server accepts delegation requests without explicit destination validation.Affected if The delegation endpoint accepts arbitrary URI targets without validation.
-
Review network egress controlsCheck firewall rules, network policies, or application-level outbound HTTP restrictions to determine if the server can make arbitrary HTTP/HTTPS requests to internal or external destinations.Affected if The server has unrestricted outbound HTTP/HTTPS capability and Operation Delegation is active.
-
Search for metadata service access patternsReview server logs, network traffic, or access patterns for connections to cloud metadata endpoints (e.g., 169.254.169.254) or internal services that should not be reachable.Affected if Evidence exists of outbound requests to internal/cloud metadata services initiated by the BaSyx server.
The environment is affected if Eclipse BaSyx Java Server SDK versions before 2.0.0-milestone-10 are in use with Operation Delegation feature enabled, allowing the server to make unrestricted HTTP POST requests to arbitrary destinations.
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.
dbcve · scopedUpgrade to Eclipse BaSyx Java Server SDK version 2.0.0-milestone-10 or later, which should include proper destination URI validation. Implement network segmentation and outbound firewall rules as a compensating control until the patch is applied.
2.0.0-milestone-10 or later
- Identify the current Eclipse BaSyx Java Server SDK version in use by checking project dependencies (e.g., pom.xml, build.gradle, or Maven/Gradle manifests)
- Locate all runtime deployments of the BaSyx server component across development, staging, and production environments
- Upgrade the Eclipse BaSyx Java Server SDK dependency to version 2.0.0-milestone-10 or later in the project's dependency management file
- Rebuild and recompile the application to ensure the new SDK version is integrated
- Update any integration tests that exercise the Operation Delegation feature to verify the URI validation is now enforced
- Deploy the rebuilt application to the affected environments
- Validate that the Operation Delegation feature correctly rejects requests to arbitrary URIs and only allows valid, expected endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7412 — 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-7412 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