Join our Newsletter — 33% off our NHI Course
Home› Glossary› Threats, Abuse & Incident Response› CVE-2021-35587 (Oracle Fusion Middleware Unspecified)
Threats, Abuse & Incident Response

CVE-2021-35587 (Oracle Fusion Middleware Unspecified)

← Back to Glossary
By NHI Mgmt Group Updated October 17, 2026 Domain: Threats, Abuse & Incident Response

CVE-2021-35587 is an unspecified vulnerability in Oracle Fusion Middleware. CISA added it to the Known Exploited Vulnerabilities catalogue on 28 November 2022, which means attackers have used it in real attacks. Oracle Fusion Middleware Access Manager allows an unauthenticated attacker with network access via HTTP to takeover the Access Manager product.

What This Vulnerability Means in Oracle Fusion Middleware

CVE-2021-35587 is an unspecified vulnerability in Oracle Fusion Middleware, specifically affecting Access Manager, where an unauthenticated attacker with HTTP network access can take over the product. That combination makes the issue dangerous even before an organisation sees obvious signs of misuse, because exposure can exist wherever the service is reachable.

For readers tracking the record itself, the authoritative entry is the CVE Program, and the public vulnerability record should be cross-checked in the NIST National Vulnerability Database alongside Oracle’s own advisory for exact product guidance.

Why This Exposure Is Operationally Dangerous

An unauthenticated, network-reachable takeover condition is especially serious in an access control product because the service sits close to trust decisions, session handling, and administrative pathways. If an attacker can influence the product before normal authentication barriers apply, the compromise may become a foothold for broader identity, application, or infrastructure abuse.

The practical danger is not just service disruption. A successful exploit can undermine the integrity of access decisions and may expose tokens, sessions, configuration, or downstream systems that rely on the product’s trust boundary. Oracle Cloud breach claim 2025 is a useful adjacent reference point for why access-management components are high-value targets when compromise is alleged or confirmed.

How Organisations Check Exposure and Reduce Attack Surface

Exposure assessment starts with asset inventory: know where Oracle Fusion Middleware and Access Manager are deployed, whether they are internet-facing, and whether they are reachable from untrusted networks. That should be paired with vendor advisories and KEV monitoring, because an entry in the exploited catalogue changes prioritisation from “known issue” to “known active attack path”.

Where patching is not immediate, organisations should reduce reachability, tighten segmentation, and review whether any management or access paths are unnecessarily exposed over HTTP. The Vulnerability Management Guide is a practical companion for prioritising KEV-listed issues, while Oracle-specific remediation details should still come from Oracle itself.

Detection, Remediation, and Trust Recovery After Exploitation

Once a product like Access Manager may have been used for takeover, detection needs to look beyond the vulnerability banner and into evidence of control-plane abuse, unusual authentication behaviour, configuration change, and post-exploitation movement. The absence of a confirmed alert does not mean the system was untouched if the service was reachable during the vulnerable window.

After remediation, review whether sessions, signing material, administrative credentials, and any downstream secrets that were exposed through the compromised path should be rotated or invalidated. If the product mediated access to other systems, assume trust may have been inherited by those systems until the environment is revalidated. The State of NHI & AI Agent Breach Report 2026 provides broader context on why compromise of access-bearing material often propagates beyond the first system.

Risk and Threat Considerations

An exploited Access Manager issue can become a gateway to privilege escalation, session abuse, or wider identity compromise because the vulnerable component often sits inside a trust chain rather than at the edge. If the service is internet-facing, the risk is materially higher because attackers can probe it directly and repeatedly.

Failure mechanism: The attacker reaches the product over HTTP, triggers the unauthenticated takeover condition, and then uses the compromised control point to manipulate access decisions or harvest trust-bearing material.

Impact: Organisations can face account compromise, unauthorised access, downstream lateral movement, and the need to treat related credentials, sessions, and keys as potentially exposed.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

CIS Controls v8 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
CIS Controls v8CIS-7 — Continuous Vulnerability ManagementThis CVE is a known exploited vulnerability requiring prioritised remediation and exposure tracking.
Recommendation — Prioritise, track, and remediate the KEV-listed issue before lower-risk backlog items.
NIST SP 800-53 Rev 5RA-5 — Vulnerability Monitoring and ScanningThe subject requires identifying exposure, validating reachability, and monitoring known vulnerabilities.
IA-5 — Authenticator ManagementPost-exploitation recovery may require rotating or invalidating credentials and related authenticators.
SC-7 — Boundary ProtectionThe issue is materially worsened when the service is reachable over the network, especially from untrusted segments.
Recommendation — Continuously scan for the affected product and verify whether exposed instances remain reachable. Rotate or invalidate exposed authenticators, tokens, and related secret material after confirmed compromise. Restrict network reachability to the vulnerable service and remove unnecessary internet exposure.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 17, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org