CVE-2026-35261
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 Access Manager product of Oracle Fusion Middleware (component: Authentication Engine). Supported versions that are affected are 12.2.1.4.0 and 14.1.2.1.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Access Manager. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Access Manager accessible data as well as unauthorized read access to a subset of Oracle Access Manager accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 confidenceVulnerability in Oracle Access Manager's Authentication Engine allows unauthenticated attackers with network access via HTTP to compromise the system. Successful exploitation grants unauthorized read access to a subset of data as well as unauthorized update, insert, or delete access to some accessible data. The attack requires no authentication and has low complexity.
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.1.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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Verify Oracle Access Manager versionCheck the installed Oracle Access Manager version against the affected versions 12.2.1.4.0 and 14.1.2.1.0. Use Oracle OPatch or check the OAM installation directory for version information.Affected if The installed version equals 12.2.1.4.0 or 14.1.2.1.0 exactly.
-
Confirm OAM Authentication Engine is network accessibleDetermine if Oracle Access Manager authentication endpoints (typically on ports 7001, 7002, or custom OAM ports) are exposed to network access. Review firewall rules, load balancer configurations, or reverse proxy settings that expose OAM interfaces.Affected if OAM authentication interfaces are reachable from untrusted networks or the internet.
-
Check for unauthenticated HTTP access to OAM endpointsReview access logs for Oracle Access Manager (OAM logs typically in $ORACLE_HOME/user_projects/domains/...) for requests to authentication endpoints that occur without valid session tokens or credentials.Affected if HTTP requests to OAM authentication URLs succeed without authentication headers or session cookies.
-
Inspect authentication audit logs for anomaliesExamine Oracle Access Manager audit and access logs for patterns indicating unauthenticated or failed authentication attempts, especially from external IP addresses or unusual access patterns.Affected if Logs show authentication attempts that bypass normal login flows or exhibit low-complexity attack patterns.
-
Review data access patterns for unauthorized operationsMonitor database or directory audit logs connected to Oracle Access Manager for unauthorized SELECT, INSERT, UPDATE, or DELETE operations that correlate with unauthenticated HTTP activity.Affected if Data modification or read operations occur without corresponding authenticated session records.
Your environment is affected if Oracle Access Manager version 12.2.1.4.0 or 14.1.2.1.0 is installed AND the OAM authentication engine is network accessible, allowing unauthenticated HTTP requests to reach the system.
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.
dbcve · scopedApply Oracle security patches for version 12.2.1.4.0 or 14.1.2.1.0 when available. Until patched, restrict network access to Oracle Access Manager interfaces and monitor for unauthorized authentication attempts or anomalous data access patterns.
Oracle Access Manager 12.2.1.4.x or 14.1.2.x to the latest respective patch bundle (apply Oracle CPU that addresses CVE-2026-35261)
- 1. Identify your current Oracle Access Manager deployment version (12.2.1.4.0 or 14.1.2.1.0)
- 2. Navigate to Oracle Support and search for Oracle Access Manager patches related to CVE-2026-35261
- 3. Apply the appropriate Oracle Critical Patch Update (CPU) that includes the fix for this vulnerability
- 4. For version 12.2.1.4.0, upgrade to the latest 12.2.1.x version available in the Oracle Fusion Middleware 12c release stream
- 5. For version 14.1.2.1.0, upgrade to the latest 14.1.x version available in the Oracle Fusion Middleware 14c release stream
- 6. After applying the patch/upgrade, restart the Oracle Access Manager services in the correct order
- 7. Verify the fix by testing authentication flows and confirming the vulnerability is no longer exploitable
- 8. Review Oracle Access Manager audit logs to ensure no exploitation occurred prior to patching
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35261 — 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-35261 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