dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-26074

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-30
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
Orkes Conductor v3.21.11 allows remote attackers to execute arbitrary OS commands through unrestricted access to Java classes.

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

Orkes Conductor v3.21.11 contains a critical vulnerability where unrestricted access to exposed Java classes allows remote unauthenticated attackers to execute arbitrary operating system commands, likely through unsafe reflection or deserialization mechanisms.

MitigationUpgrade to a patched version of Orkes Conductor and/or implement network-level access controls to restrict exposure of the vulnerable Java class endpoints.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Determine Orkes Conductor version
    Check the Conductor UI footer for the version number, or query the /api/version endpoint, or inspect server startup logs
    Affected if Version is 3.21.11 or any earlier 3.x release prior to the patched version
  2. Verify authentication is enforced
    Attempt to access the Conductor UI or API endpoints (such as /api/workflow) without providing credentials
    Affected if The interface is accessible without any authentication token or login prompt
  3. Check network exposure of admin interface
    Review firewall rules, reverse proxy configuration, or cloud security groups to determine if the Conductor UI port (typically 8080 or 443) is exposed to the internet or untrusted networks
    Affected if The administrative interface is reachable from public or untrusted network segments without IP or VPN restrictions
  4. Inspect Java class exposure settings
    Review Conductor configuration files (application.yml or conductor.json) for any settings related to 'script', 'java', or 'executable' workflow task types that may be enabled without access controls
    Affected if Executable task types or unsafe Java class access is enabled without role-based restrictions

A user is affected if their Orkes Conductor installation is version 3.21.11 or earlier and the admin interface is accessible without authentication from an untrusted network.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Orkes Conductor and/or implement network-level access controls to restrict exposure of the vulnerable Java class endpoints.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26074 — 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-2025-26074 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