01 / CONFIRMED CONTEXT

What Oracle has published.

Oracle’s November pre-release announcement lists 11 Java SE fixes, says all may be exploitable remotely without credentials, and gives 8.1 as the group’s highest CVSS 3.1 score. Oracle Java SE 17.0.21 appears in its affected-build list. None of those statements assigns this CVE to a fix.

02 / OPEN QUESTIONS

What remains unverified.

  • Whether Oracle’s 11 fixes include CVE-2026-114938.
  • The claimed Java 17-only affected range and memory-corruption mechanism.
  • The reported pre-authentication code execution and CVSS 4.0 score of 9.2.
  • A vendor-confirmed fixed build, public PoC or reliable exposure test for this ID.

Do not transfer Oracle’s 8.1 group score to this individual ID or treat the reported 9.2 as a verified Oracle score.

03 / ACTION NOW

Inventory and follow the vendor update.

Identify live Java runtimes and exposed services. Prepare a change for the applicable vendor security release, then verify the updated JVMs. Use temporary network and privilege controls where deployment takes time.

Open the patch workflow →
04 / PROVENANCE

Source boundary.

Oracle’s Java SE pre-release summary is the source for the confirmed statements. The community discussion is a lead, not validation. See all links and review notes →

Reviewed 17 November 2026. This is a static snapshot and may be overtaken by the full advisory.