CVE-2026-35243
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 Application Development Framework (ADF) product of Oracle Fusion Middleware (component: ADF Faces). Supported versions that are affected are 12.2.1.4.0 and 14.1.2.0.0. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Application Development Framework (ADF) executes to compromise Oracle Application Development Framework (ADF). Successful attacks of this vulnerability can result in takeover of Oracle Application Development Framework (ADF). CVSS 3.1 Base Score 7.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
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 confidenceVulnerability in Oracle ADF Faces component of Oracle Fusion Middleware allows a low-privileged attacker with local access to the infrastructure to compromise Oracle ADF, potentially achieving complete system takeover with high impact to confidentiality, integrity, and availability.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 ADF installation locationLocate the Oracle Fusion Middleware home directory (typically $ORACLE_HOME) and look for ADF libraries in the oracle_common or modules directory. Check for adf.jar, adf-faces.jar, or similar Oracle ADF libraries.Affected if The installation uses Oracle Application Development Framework libraries from Oracle Fusion Middleware
-
Determine installed ADF versionCheck the version of Oracle ADF libraries. In the Oracle Fusion Middleware home, examine META-INF/MANIFEST.MF files within adf*.jar files, or use Oracle Enterprise Manager to view installed component versions. Also check the documentation or patch inventory for the ADF version.Affected if The installed Oracle ADF version is exactly 12.2.1.4.0 or exactly 14.1.2.0.0
-
Verify ADF Faces component is in useConfirm that Oracle ADF Faces is deployed and actively used. Check application deployment descriptors (web.xml, adfc-config.xml, faces-config.xml) for ADF Faces servlet definitions and check if the application uses ADF Faces components/ RichFaces.Affected if ADF Faces component is deployed and running within the ADF application
-
Check application accessibilityDetermine if the ADF application is accessible over the network or if attackers could obtain local access to the server infrastructure. Review network exposure and physical access controls to the Oracle WebLogic Server hosting ADF applications.Affected if The server hosting Oracle ADF is accessible to low-privileged users either physically or via network
The environment is affected if Oracle ADF version 12.2.1.4.0 or 14.1.2.0.0 is installed, ADF Faces component is deployed, and attackers could potentially gain local access to the infrastructure.
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's latest Critical Patch Update for Oracle Fusion Middleware to obtain the security fix for affected versions 12.2.1.4.0 and 14.1.2.0.0; until patches are available, restrict physical and logical access to servers running Oracle ADF and follow least-privilege principles for ADF application users.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35243 — 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-35243 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