CVE-2026-34284
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 · uneditedVulnerability in the Oracle Business Process Management Suite product of Oracle Fusion Middleware (component: Human workflow 11g+). Supported versions that are affected are 12.2.1.4.0 and 14.1.2.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Business Process Management Suite. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Business Process Management Suite, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Business Process Management Suite accessible data as well as unauthorized read access to a subset of Oracle Business Process Management Suite accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).
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 confidenceUnauthenticated HTTP vulnerability in Oracle BPM Suite's Human Workflow component (versions 12.2.1.4.0 and 14.1.2.0.0) allows remote attackers to achieve unauthorized read access and partial write/delete access to data. The required human interaction (UI:R) combined with scope change (S:C) suggests a client-side injection flaw likely enabling indirect attacks against other products.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 12.2.1.4.0= 14.1.2.0.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Oracle BPM Suite installationLocate Oracle BPM Suite installation directory. Common paths include $ORACLE_HOME/bpm on Oracle WebLogic servers. Check for presence of 'Oracle_BPM' or 'bpm' directories in the Oracle middleware home.Affected if Oracle BPM Suite is installed on the system
-
Determine installed BPM Suite versionCheck the version file or manifest in the BPM installation directory. Run: grep -r '12.2.1.4.0\|14.1.2.0.0' $ORACLE_HOME/bpm or examine the OPatch inventory: $ORACLE_HOME/OPatch/opatch lsinventory -detail | grep -i bpmAffected if Installed version matches exactly 12.2.1.4.0 or 14.1.2.0.0
-
Verify Human Workflow component is deployedCheck WebLogic Administration Console for deployed 'Human Workflow' or 'bpm-workflow' ear/lib deployments. Alternatively, inspect: ls $ORACLE_HOME/bpm/modules/oracle.bpm.workflow* 2>/dev/nullAffected if Human Workflow component is deployed and enabled on the WebLogic server
-
Confirm HTTP access to BPM interfacesTest HTTP/HTTPS accessibility of common BPM endpoints: curl -I http://<host>:<port>/bpm/services or http://<host>:<port>/bpm/workspace. Check WebLogic HTTP channel configuration for BPM-managed servers.Affected if BPM HTTP endpoints are externally accessible without authentication required
-
Check for unauthenticated HTTP endpoint exposureSend unauthenticated HTTP requests to Human Workflow endpoints such as: curl -s http://<host>:<port>/bpm/services/HumanTaskService?wsdl or curl -s http://<host>:<port>/bpm/workspace/. Verify if responses return without 401/403 authentication errors.Affected if Human Workflow HTTP endpoints respond to unauthenticated requests with valid SOAP/XML content
User is affected if Oracle BPM Suite versions 12.2.1.4.0 or 14.1.2.0.0 are installed with the Human Workflow component exposed via HTTP and accessible without authentication.
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 dataApply Oracle Critical Patch Updates for Oracle Business Process Management Suite; until patches are available, restrict network access to BPM interfaces and monitor for anomalous HTTP requests.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34284 — 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-34284 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