dbcve.org
CWE-610Weakness · CWE-610

CVE-2026-2536

MEDIUM · 6.3 CVSS v3.1 Published 2026-02-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
A vulnerability was determined in opencc JFlow up to 20260129. This affects the function Imp_Done of the file src/main/java/bp/wf/httphandler/WF_Admin_AttrFlow.java of the component Workflow Engine. This manipulation of the argument File causes xml external entity reference. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.

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

An XML External Entity (XXE) vulnerability exists in the Imp_Done function of WF_Admin_AttrFlow.java in opencc JFlow workflow engine. The function processes a File argument without properly disabling external entity resolution, allowing an attacker to inject malicious XML containing external entity references for file disclosure or server-side request forgery.

MitigationDisable external entity processing in the XML parser configuration used by the Imp_Done function. Implement secure XML parsing by disabling DTDs, external entities, and external entity resolution in the XML processing library.

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 checks

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

  1. Identify if JFlow workflow engine is installed
    Search the system for files named WF_Admin_AttrFlow.java or search for 'JFlow' or 'opencc' in installed applications and libraries
    Affected if The WF_Admin_AttrFlow.java file exists in the environment, indicating JFlow is present
  2. Locate and inspect the Imp_Done function
    Find the WF_Admin_AttrFlow.java file in the codebase and examine the Imp_Done method to see how it handles File arguments and XML processing
    Affected if The Imp_Done function processes XML from a File argument without secure XML parser configuration
  3. Check XML parser configuration in the affected function
    Review the XML parsing code within Imp_Done to determine if external entity resolution is explicitly disabled (look for features like 'XMLConstants.ACCESS_EXTERNAL_DTD', 'XMLConstants.ACCESS_EXTERNAL_SCHEMA', or similar security settings)
    Affected if The XML parser is configured without disabling external entities or DTD processing
  4. Verify if the vulnerable code path is reachable
    Determine if the Imp_Done function can be invoked via user input, API endpoints, or administrative interfaces in the deployed application
    Affected if The function accepts user-supplied or externally sourced XML files that could contain malicious entity references
  5. Confirm the XML library and version in use
    Identify which XML processing library (JAXP, DOM4J, etc.) is used by the Imp_Done function and check if it supports external entity resolution controls
    Affected if The XML library does not have external entity resolution disabled by default or the code does not explicitly disable it

You are affected if JFlow workflow engine with WF_Admin_AttrFlow.java is present and the Imp_Done function processes XML files without explicitly disabling external entity resolution in the parser configuration.

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

Disable external entity processing in the XML parser configuration used by the Imp_Done function. Implement secure XML parsing by disabling DTDs, external entities, and external entity resolution in the XML processing library.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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