dbcve.org
Identity ManagerApplication · Oracle

CVE-2026-35269

HIGH · 7.5 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Vulnerability in the Identity Manager product of Oracle Fusion Middleware (component: REST WebServices). 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 Identity Manager. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Identity Manager accessible data. CVSS 3.1 Base Score 7.5 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 · high confidence

Unauthenticated REST WebServices vulnerability in Oracle Identity Manager allows remote attackers via HTTP to create, delete or modify critical data without credentials. The flaw affects REST API endpoints in versions 12.2.1.4.0 and 14.1.2.1.0, with high integrity impact due to unauthorized data modification capabilities.

MitigationApply Oracle security patches for this vulnerability when released. Until then, restrict network access to Identity Manager REST endpoints via firewall or WAF rules, and monitor for unauthorized modification requests.

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
Identity ManagerApplication
Affected:= 12.2.1.4.0= 14.1.2.1.0

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle Identity Manager installation and version
    Locate the Oracle Identity Manager installation directory and check for version information in product documentation, about pages in the OIM admin console, or installation logs. Oracle Identity Manager version is typically displayed in the console header or can be retrieved using Oracle Enterprise Manager or WLST commands.
    Affected if The installed version matches exactly 12.2.1.4.0 or 14.1.2.1.0
  2. Confirm REST API endpoints are enabled and accessible
    Verify that REST WebServices endpoints are enabled in the Oracle Identity Manager configuration. This can be checked through the OIM admin console under system configuration, or by reviewing the deployed web services configuration files in the Oracle WebLogic Server console.
    Affected if REST API endpoints are enabled and accessible without authentication requirements
  3. Check network accessibility of OIM REST services
    Determine if the Oracle Identity Manager server is directly accessible via HTTP/HTTPS from untrusted networks. Verify firewall rules, load balancer configurations, and WebLogic listener bindings to confirm whether OIM REST endpoints can be reached from external networks.
    Affected if The OIM REST endpoints are exposed to untrusted network segments or the internet without proper network filtering
  4. Review access control configuration for REST endpoints
    Inspect the Oracle WebLogic security configuration and OIM policy settings to verify whether REST API endpoints require authentication. Check for any misconfigured policies that might allow unauthenticated access to create, modify, or delete operations.
    Affected if REST API endpoints permit unauthenticated access to data modification operations

A user is affected if they have Oracle Identity Manager version 12.2.1.4.0 or 14.1.2.1.0 with REST API endpoints accessible over HTTP without authentication controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle security patches for this vulnerability when released. Until then, restrict network access to Identity Manager REST endpoints via firewall or WAF rules, and monitor for unauthorized modification requests.

Recommended fix Moderate confidence

Upgrade to Identity Manager 14.1.3.x or later stable release, or apply the latest Oracle Critical Patch Update containing the fix for CVE-2026-35269

  1. 1. Identify the current Oracle Identity Manager version by checking the Oracle WebLogic Server administration console or running 'java -jar oracle_common/modules/internal/oracle.iam.version.jar'
  2. 2. Download and apply the latest Oracle Critical Patch Update (CPU) that addresses this vulnerability. Check Oracle's Critical Patch Updates advisory for CVE-2026-35269
  3. 3. If a specific patch is available from Oracle Support, apply it using OPatch: run 'opatch apply -ph <patch_directory>'
  4. 4. After applying the patch, restart the Oracle Identity Manager managed servers and the WebLogic Administration Server
  5. 5. Verify the fix by confirming the REST WebServices endpoints are only accessible to authenticated users and that the vulnerability is resolved
  6. 6. Alternatively, upgrade to a later stable version of Identity Manager (14.1.3.x or later) that includes the security fix
  7. 7. If immediate patching is not possible, implement network-level access controls to restrict HTTP access to Identity Manager REST services to trusted IP addresses only
Caveat Oracle major/minor version upgrades may require compatibility testing with integrated systems and custom plugins; review Oracle's upgrade documentation for breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Identity Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35269 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35269 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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