Oracle JDeveloper EUVD-2026-79658

Exploitation requires three concrete things: network reachability to the Resource Catalog Services HTTP endpoint of an Oracle JDeveloper 12.2.1.4.0 or 14.1.2.0.0 deployment; a valid low-privileged account on that deployment (the CVSS PR:L rating means authentication is mandatory - this is not anonymous); and the Resource Catalog component remaining enabled and exposed rather than firewalled or removed. It does not require user interaction (UI:N), does not require administrative credentials, and does not depend on a particular non-default configuration flag beyond the component's presence. Limiting factors: environments where JDeveloper is a standalone desktop IDE with no network-exposed Resource Catalog service are not remotely reachable; environments that front the service with an authenticating proxy, segment it to a developer VLAN, or remove the component entirely are materially harder to exploit; and a deployment with no low-privileged accounts available to an attacker cannot satisfy the authentication prerequisite.

The CVSS 3.1 base score of 8.8 is driven by network reachability, low attack complexity, no user interaction and total C/I/A impact, but it is held below 9.0 only because a low-privileged account (PR:L) is required - so this is not a pre-auth internet-facing smash-and-grab. Because no EPSS score, KEV listing or public exploit code was provided, there is no evidence of active exploitation and no reason to treat it as a wormable emergency; the practical decision is to patch within a normal critical-update cycle, and even a mid-sized municipal IT team in olsztyn should treat this as urgent if their JDeveloper/Resource Catalog endpoints are reachable from anything wider than a trusted developer VLAN. The signals are internally consistent in severity but incomplete in exploitation evidence: CVSS says 'easily exploitable', the source metadata says nothing about POC or in-the-wild use, and the 'Information Disclosure' tag conflicts with a full-integrity-and-availability impact described as 'takeover', which should be treated as an auto-tagging artifact rather than a downgrade. Net assessment: high real-world risk where the service is exposed and accounts are shared or weakly managed, medium where JDeveloper is confined to isolated developer networks.

An attacker who already holds a low-privileged JDeveloper or Fusion Middleware account - an insider, a compromised developer workstation, or a contractor credential - sends a crafted HTTP request to a reachable Resource Catalog Services endpoint, exploiting the defect to run logic with service-level privileges. Because the vector needs no user interaction and the complexity is low, the step from a valid low-privileged login to full control of the JDeveloper instance is short, giving the attacker read/write access to project artifacts, deployment credentials and any resources the service can touch. No public proof-of-concept was identified in the supplied data, so the technique is presumed to require attacker-developed tooling.