CVE-2026-115086

waiting for further signalsZero needs more public information before it can validate it.

GHSA-4mhh-9634-g8j2 ↗EUVD-2026-127914 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Oracle Corporation Oracle Hyperion Planning 11.2.26.0.000
ETK-2026-4718Zero's internal tracking ID, independent of the CVE number., permanent identifier
20h 31msince last run
10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+4h02m
0
+2h
+6h
+8h
+10h
+12h

description

Oracle Hyperion Planning 11.2.26.0.000 has an authentication weakness affecting its RMI-exposed service. An unauthenticated remote attacker may be able to take control of the Planning deployment if they can reach that service over the network.

mitigation

Apply Oracle's relevant security update for Hyperion Planning after confirming the applicable supported release. Until it is patched, limit RMI access to trusted administrative hosts and block it from untrusted networks.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-17 21:32Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-17 21:32Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-115086

{
  "etk_id": "ETK-2026-4718",
  "cve_id": "CVE-2026-115086",
  "display_id": "CVE-2026-115086",
  "ghsa_id": "GHSA-4mhh-9634-g8j2",
  "euvd_id": "EUVD-2026-127914",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authentication in Oracle Hyperion Planning",
  "summary": "Oracle Hyperion Planning 11.2.26.0.000 has an authentication weakness affecting its RMI-exposed service. An unauthenticated remote attacker may be able to take control of the Planning deployment if they can reach that service over the network.",
  "mitigation": "Apply Oracle's relevant security update for Hyperion Planning after confirming the applicable supported release. Until it is patched, limit RMI access to trusted administrative hosts and block it from untrusted networks.",
  "vendor": "Oracle Corporation",
  "product": "Oracle Hyperion Planning",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "11.2.26.0.000"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Oracle Hyperion Planning",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 9.589317366666666,
  "t0_at": "2026-11-17T21:32:54.188000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-17T21:32:54.188000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-17T21:32:54.188000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-115086"
    }
  }
}

published 2026-11-17 22:53Z
last change 2026-11-18 21:43Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.