CVE-2026-6125
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 · uneditedA security flaw has been discovered in Dromara warm-flow up to 1.8.4. Impacted is the function SpelHelper.parseExpression of the file /warm-flow/save-json of the component Workflow Definition Handler. The manipulation of the argument listenerPath/skipCondition/permissionFlag results in code injection. The attack may be performed from remote. The exploit has been released to the public and may be used for attacks.
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 confidenceCode injection vulnerability in Dromara warm-flow's Workflow Definition Handler where user-controlled arguments (listenerPath, skipCondition, permissionFlag) are passed unsafely to SpelHelper.parseExpression, allowing remote attackers to inject and execute arbitrary SpEL expressions.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 warm-flow installationSearch for warm-flow JAR files in your application deployment directory, or check your build configuration (pom.xml, build.gradle) for warm-flow dependency declarationsAffected if warm-flow is present and version is below 1.8.5 (or version cannot be determined)
-
Verify exposed API endpointsInspect your application's registered REST endpoints, particularly look for /warm-flow/save-json or similar Workflow Definition Handler endpoints exposed via Spring MVC controllersAffected if The save-json endpoint or Workflow Definition Handler endpoints are publicly accessible without authentication
-
Confirm SpelHelper usageSearch codebase for SpelHelper.parseExpression calls and verify if listenerPath, skipCondition, or permissionFlag parameters from HTTP requests flow into these calls without sanitizationAffected if User input parameters are passed directly to SpelHelper.parseExpression without input validation
-
Review workflow definition configurationsExamine any stored or submitted workflow definitions to see if the listenerPath, skipCondition, or permissionFlag fields accept dynamic SpEL expressions as valuesAffected if Workflow definitions allow arbitrary SpEL expressions in these fields without sandboxing
Your environment is affected if warm-flow version is below 1.8.5 AND the Workflow Definition Handler endpoint (especially /warm-flow/save-json) is accessible with user-controlled listenerPath, skipCondition, or permissionFlag parameters being passed to SpelHelper.parseExpression.
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.
From vendor dataUpgrade to warm-flow version 1.8.5 or later to obtain the patch. Alternatively, implement strict input validation on the /warm-flow/save-json endpoint and restrict network access until the upgrade is applied.
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6125 — 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-6125 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