Unauthenticated code execution via exposed JMXP deserialization
Published Mar 17, 2026 · Updated Mar 17, 2026
Missing authentication in JMX in TIBCO BPM Enterprise 4.3 through 4.3.4 allows remote attackers to execute unauthorized actions. With secure management communication disabled by default, the JMXP endpoint accepts unauthenticated connections that invoke deserialization in management components. Reachability requires adjacent-network access to the JMX service; exploitation permits code execution in the affected system's process context.
Summary
What happened
Missing authentication in JMX in TIBCO BPM Enterprise 4.3 through 4.3.4 allows remote attackers to execute unauthorized actions. With secure management communication disabled by default, the JMXP endpoint accepts unauthenticated connections that invoke deserialization in management components. Reachability requires adjacent-network access to the JMX service; exploitation permits code execution in the affected system's process context.
The record
- CVE
- CVE-2026-3207
- Published
- Mar 17, 2026
- Updated
- Mar 17, 2026
- Vendor
- TIBCO Software Inc.
- Product
- TIBCO BPM Enterprise
- Classifications
- CWE-306, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 17, 2026CVE publishedPublication date reported by the CVE source.
- Mar 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.3 <5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo