CVE-2026-3912
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 · uneditedInjection vulnerabilities due to validation/sanitisation of user-supplied input in ActiveMatrix BusinessWorks and Enterprise Administrator allows information disclosure, including exposure of accessible local files and host system details, and may allow manipulation of application behaviour.
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 confidenceThis is an injection vulnerability in TIBCO ActiveMatrix BusinessWorks and Enterprise Administrator caused by improper validation and sanitization of user-supplied input. The flaw allows attackers to expose local files and host system details through the application, and may enable manipulation of application behavior through injected input.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 TIBCO product installationLocate TIBCO ActiveMatrix BusinessWorks or Enterprise Administrator on the system. Check common installation paths such as /opt/tibco, C:\tibco, or use system package/query tools to list installed TIBCO software.Affected if Either TIBCO ActiveMatrix BusinessWorks or Enterprise Administrator is present on the system
-
Determine installed versionLocate version information for the TIBCO product. Check for version files in the installation directory, manifest files, or use vendor-provided command-line tools to query the installed version.Affected if The installed version falls within the vulnerable version range for this CVE
-
Verify exposed interfacesReview network configuration to determine if the application HTTP/API endpoints are accessible from untrusted networks. Check firewall rules, reverse proxy configurations, and application binding settings.Affected if The application REST/API or web interfaces are exposed to external or untrusted network sources
-
Inspect input handling logsReview TIBCO application logs for suspicious patterns, error messages indicating file access attempts, host system information leakage, or malformed user input that could indicate exploitation attempts.Affected if Logs show evidence of injection attempts or unexpected file/system information exposure
If TIBCO ActiveMatrix BusinessWorks or Enterprise Administrator is running and its interface accepts user-supplied input, compare your version against the affected range to determine if you are vulnerable to this injection flaw.
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 dataImplement strict input validation and sanitization for all user-supplied data, restrict file access permissions, and apply principle of least privilege to limit exposure of system files and details.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3912 — 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-3912 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