Oracle OpenJDK Java (CVE-2026-114938): Rapid7 product coverage and FAQ
Last updated: November 18, 2026
For a full description of the vulnerability, affected and fixed Java versions, exploitation status, and temporary mitigations, see the Rapid7 Emergent Threat Response (ETR) blog post: CVE-2026-114938: Critical Unauthenticated Remote Code Execution in Oracle OpenJDK Java .
This page explains how to use Rapid7 products to find affected systems, and answers common questions. The procedural steps presented in this documentation use the unified navigation and assume Command Platform Login is enabled for Vulnerability Management users.
1. Product coverage at a glance
| Product | Status |
|---|---|
| Exposure Command, Vulnerability Management (InsightVM), and Nexpose | Available. Refer to section 2 for available vulnerability checks |
Status update: Rapid7 has released authenticated coverage for Vulnerability Management (InsightVM), available in content version 1.1.4115.
2. Find and confirm exposure with Exposure Command, Vulnerability Management (InsightVM), and Nexpose
November 17, 2026 coverage updates
| Check ID | Check purpose |
|---|---|
| jre-memory-corruption-rce-cve-2026-114938 | To detect a vulnerability existing in Oracle Java SE |
How the checks work
This check is Authenticated, and triggers on version 17.0.6 or higher. This is focusing on software with the product name of “JRE”.
They flag:
Software with the product name “JRE”, version 17.0.6 or higher.
Step 1: Get the new content
Security Consoles with automatic content updates enabled will apply the release at their next scheduled update check.
How to update manually
With a Global Administrator account, go to Administration > Vulnerability Management > Console Administration > Console, Updates > Manual Update.
Task 1: Verify that vulnerability checks are available
Use these steps to confirm your Security Console has the content needed to detect CVE-2026-114938.
- Check your content version
- Sign in to the Security Console with an account that has Global Administrator permissions.
- Go to Administration > Vulnerability Management > Console Administration > Information.
- Review the latest vulnerability content version listed, and confirm it includes the content release for this CVE.
- Confirm checks exist for the CVE
- In the Security Console, select the search icon in the top right corner.
- Search for
CVE-2026-114938. - Confirm that results are returned for CVE-2026-114938, and the available vulnerabilities align with the Coverage updates table.
Missing CVE requires a Security Console update
If the CVE is missing, update your Security Console content and check again.
After the content is current, run a scan so your assets are assessed against the new checks.
Task 2: Rescan with a Scan Engine
Existing results don’t change until all assets are rescanned with the new content.
Scan template:
Authenticated checks only run if the site has working credentials. Configure SMB/Windows credentials for Windows hosts and SSH credentials for Linux/Unix hosts on the site. Confirm in the scan summary page or scan log that authentication succeeded. If it didn’t, authenticated checks won’t run.
(Optional) Scan for this vulnerability only
- Copy an existing scan template.
- In the template’s Vulnerability Checks settings, disable the check categories you don’t need, then add the individual checks for CVE-2026-114938. You can search by check ID, check name, or CVE ID.
- Save the template and scan your systems.
For more information, read Configuring custom scan templates (https://docs.rapid7.com/insightvm/configuring-custom-scan-templates/ ) and Selecting a scan template (https://docs.rapid7.com/insightvm/selecting-a-scan-template/ ).
Task 3: Rescan with a Rapid7 Agent (Insight Agent)
The Rapid7 Agent (Insight Agent) is a lightweight software deployed onto assets across your environment that can perform regular data collection used for vulnerability assessment, with the results displayed in your Vulnerability Management Security Console.
By default, Rapid7 Agents (Insight Agents) perform collections every 6 hours. Agent Assessments can also be triggered manually. See Run an On-Demand Scan for Vulnerabilities (https://docs.rapid7.com/insightvm/using-the-insight-agent-with-insightvm/#run-an-on-demand-scan-for-vulnerabilities ) for more information.
Agent assessments search all paths automatically with no need for additional configuration.
If you have not deployed Rapid7 Agents (Insight Agents) to your environment, please see the Rapid7 Agent (Insight Agent) install guide https://docs.rapid7.com/insight-agent/install/
To verify that Rapid7 Agents (Insight Agents) are deployed:
- From the Command Platform, go to Data Connectors > Agents.
- Navigate to Assets & Identities > Vulnerability Management > Asset Sites.
- Search for the site named ”Rapid7 Insight Agents”.
For more information, see Using the Rapid7 Agent (Insight Agent) with Vulnerability Management (https://docs.rapid7.com/insightvm/using-the-insight-agent-with-insightvm )
Step 2: Find affected assets
Filter vulnerabilities
- Go to Findings > All Findings > Vulnerability Management > **Scan and Agent Based Vulnerabilities **> Apply Filters.
- Use criteria such as CVE ID, Vulnerability Title. For details, refer to Coverage Updates.
Filter assets
- Go to Assets & Identities > Vulnerability Management > Assets > Go to Asset Search (top right).
- Use criteria such as CVE ID, Vulnerability Title, Software name.
- Once the search completes, select Create Asset Group to create a filter of Assets that can be easily referenced across reports, remediation projects, and dashboards.
Report on affected assets in the Security Console
- From Command Home, go to Reports & Dashboards > Vulnerability Management > Console Reports > Reports > Create a report.
- Choose a report type. Note that under Scope, you can select the site, asset group, tag, or assets you want to report on.
- Optionally, to scope the report to a specific vulnerability category and/or severity, go to Scope > Filter report scope based on vulnerabilities and filter by severity or category - for example, “Java”.
Generated reports are displayed under “View reports”.
Take further action if the report output is blank
A blank report output indicates that the specified vulnerabilities were not detected in your environment. However, it is recommended that you cross-reference this with the other Security Console tools outlined in this documentation to confirm scan coverage and verify zero findings.
Expected results if Java findings are present:
- Java instances with “Unknown” as the version or build
- Java instances with the associated version or build
Option A: Built-in report templates
Use these when you need a ready-made, formatted report for stakeholders.
Example reports:
- Audit Report: Detailed per-asset findings, including affected software and proof.
- Top Remediations: Prioritized fixes, useful for patching Java across many hosts.
- Executive Overview: High-level risk summary for management.
Option B: CSV Export
Use this for quick, flat data you can sort or share.
Choose Export and Select a template, such as Basic Vulnerability Check Results.
Option C: SQL Query Export
Use this for custom, precise results against the Reporting Data Model.
Choose Export > SQL Query Export.
Please see the SQL Query Examples below that can be used for reporting on Java findings:
Java Detected as a Service
SELECT DISTINCT
da.ip_address,
da.host_name,
das.port,
dp.name AS protocol,
ds.name AS service_name,
dsf.name AS service_fingerprint,
dsf.version AS service_version
FROM dim_asset_service das
JOIN dim_asset da USING (asset_id)
JOIN dim_service ds USING (service_id)
JOIN dim_protocol dp USING (protocol_id)
LEFT JOIN dim_service_fingerprint dsf USING (service_fingerprint_id)
WHERE ds.name ILIKE '%java%'
OR dsf.name ILIKE '%java%'
OR dsf.version ILIKE '%java%'
ORDER BY da.ip_address, das.port;Java Detected in a Scan Fingerprint
SELECT DISTINCT da.ip_address AS "IP Address",
da.host_name AS "Hostname",
das.port AS "Port",
dasc.name AS "Attribute",
dasc.value AS "Value"
FROM dim_asset da
JOIN dim_asset_service das ON das.asset_id = da.asset_id
JOIN dim_asset_service_configuration dasc ON dasc.service_id = das.service_id
WHERE dasc.value ~* 'java'
ORDER BY da.host_name, das.port;Java Detected as Software
SELECT DISTINCT
da.ip_address,
da.host_name,
dsoft.vendor AS software_vendor,
dsoft.name AS software_name,
dsoft.version AS software_version
FROM dim_asset_software dasoft
JOIN dim_asset da USING (asset_id)
JOIN dim_software dsoft USING (software_id)
WHERE dsoft.name ILIKE '%java%'
OR dsoft.name ILIKE '%openjdk%'
ORDER BY da.ip_address, dsoft.name;Java Detected as a Vulnerability
SELECT
da.ip_address,
da.host_name,
dv.title,
dv.severity,
dv.cvss_score,
favi.port
FROM fact_asset_vulnerability_instance favi
JOIN dim_asset da USING (asset_id)
JOIN dim_vulnerability dv USING (vulnerability_id)
WHERE dv.title ILIKE '%CVE-2026-114938%'
ORDER BY da.ip_address;Dashboard and Query Builder reporting
To apply a query to a dashboard card, open Dashboards, select Expand Card, and use Add Criteria.
To open Query Builder
- Go to Reports & Dashboards > Vulnerability Management > Vulnerability Dashboard.
- Select the magnifying glass/menu icon in the upper right corner next to the account icon.
Build the query in Standard mode
Reference an Asset Group
- Select Add.
- Select a category, then the asset.groups field. You can also type a keyword in the search bar to find it.
- Select an operator and the asset group name (for example, “Java Servers”).
- Select Apply and Save.
Reference a CVE ID
- Select Add again.
- Select the vulnerability.cveIds field, an operator, and the CVE ID (CVE-2026-114938).
- Select Apply and Save.
Reference a Software
- Select Add again.
- Select the asset.software.vendor field, an operator, and Oracle or OpenJDK as the software name.
- Select Apply and Save.
More granular querying can be performed in Expert Mode.
For more information, read Query Builder https://docs.rapid7.com/insightvm/query-builder/
To apply the saved query to a Dashboard
- Go to Reports & Dashboards > Vulnerability Management > Vulnerability Dashboard.
- Select Load Dashboard Query.
3. Find and confirm exposure with Attack Surface Management (Surface Command)
Attack Surface Management (Surface Command) can ingest data from other sources, including Rapid7 products.
Confirm data source configuration
Confirm your vulnerability data source (for example, your Vulnerability Management (InsightVM) or Rapid7 connector) is connected and syncing.
- Go to Data Connectors > Attack Surface Management > Connectors.
- Search for Rapid7 and verify these connectors exist.
- Go to Data Connectors > Attack Surface Management > Import Feeds.
- Search for Rapid7 and verify these connectors are configured to import and have done a recent import. “Run now” will force the connector to run manually.
Querying
Queries are built from an asset type plus a search pattern of property filters and relationships to other asset types.
To search for assets impacted by a specific vulnerability:
- Go to the Assets & Identities > Attack Surface Management > Workspace.
- Select + Query, and then select the asset type “Asset”.
- Click the three dots on Assets > Add relationship > choose Exposure (for other products, this will be Finding or Vulnerability)
- Click the three dots on Exposure > Filter result > CVEs > Select operator (Use contains for CVE ID, Title, etc.)
- *Turn on Distinct to remove duplicates. This can be found at the top right of the page.
To run the query, select the Play icon. To save to query, select the Save button. This will be available under Queries.
Widgets and Dashboards
Dashboards contain widgets, and widgets are built from saved queries.
Build Widgets
- Go to Assets & Identities > Attack Surface Management > Queries.
- Select the saved query, and then select Widgets.
- Select + Widget.
Build Dashboards
- Go to Reports & Dashboards > Attack Surface Management > Attack Surface Dashboard.
- Select + Dashboards.
- Select + Widgets to add your widgets.```
- You can also edit existing dashboards using the pencil icon in the top right.
Widgets are shared across your Surface Command instance, so any user can use or copy them.
Editing one widget can affect other dashboards that use it.
Edits to default dashboards are overwritten by connector updates, so build custom dashboards instead.
4. Remediation Hub
Remediation Hub offers a couple of quick ways to view remediations for all affected assets across Vulnerability Management (InsightVM), Cloud Security (InsightCloudSec), and supported Attack Surface Management (Surface Command) connectors.
For details on using Remediation Hub, see Prioritize and act on remediations .
View affected assets using the Emergent Threats banner
- Go to Response & Remediation > Remediation Hub.
- Expand the Emergent Threats banner at the top of the page.
- Select View Remediation next to the CVE you want to examine.
The remediation details panel opens for the CVE where you can browse affected assets, remediation guidance, and CVE properties.
View affected assets using filters
- Go to Response & Remediation > Remediation Hub.
- Select Filters.
- Add a filter:
- Select Remediations for Criteria.
- Select contains for Operator.
- Enter
javafor Value.
- Select Apply.
5. Bulk Export MCP
Rapid7 provides a free, open-source MCP server and agent skill for bulk export.
Bulk export creates a local offline replica of your Rapid7 Vulnerability Management (InsightVM) data that an AI assistant can query quickly, which reduces the token cost and the time it takes to receive an answer.
You can ask natural-language questions about your Java exposure, such as which assets are affected by CVE-2026-114938, without needing to write queries.
Before you begin
- Create a Rapid7 API key with the permissions that Bulk Export needs, and note your Platform region. You can decide on a user key (to control what the API key can see) or an org key (to allow the API key to access all data within the org).
- Confirm your vulnerability content is current and recent scans have completed, so the export includes the Java CVE.
For more information about API keys, read Manage Platform API Keys (https://docs.rapid7.com/insight/managing-platform-api-keys/ ).
Install and configure
Installation, configuration, skill setup, and verification steps differ by AI client and are maintained by Rapid7 in the project README. Follow the instructions here:
Rapid7 Bulk Export MCP Server on GitHub
Store your API key in a secrets manager rather than in plain text on disk. The README explains how.
Example prompt
Once the server and skill are connected, try this prompt:
Load the latest vulnerability data from Rapid7, then help me assess our exposure to CVE-2026-114938 (a critical Oracle OpenJDK Java vulnerability allowing unauthenticated remote code execution).
Use this Rapid7 blog post for the fixed versions and mitigation guidance: https://www.rapid7.com/blog/post/etr-cve-2026-114938-reported-critical-pre-authentication-remote-code-execution-java-17/
1. List every asset with a finding for the CVE. Include asset name,
IP address, operating system, the CVE ID, severity, and the date
first found.
2. List assets with Java installed, as per the impacted and fixed version in the Rapid7 Blog Post on Java.
3. Group results by site or owner, and flag assets that are internet
facing or business critical, where that data is available.
4. Rank the top 20 assets to patch first and explain why.
5. Summarise how many assets are affected, how many have already been
remediated, and what has changed since last week.
Tell me which fields were missing from the data, and do not guess.
Present the results as a table I can export to CSV.Follow-up prompts
- Which affected assets are tagged as production?
- Show assets where Java remediation was recorded, and the date.
- Write a short summary of our Java exposure for a non-technical audience.
Best practice for working with AI clients
- Validate answers. Spot-check the results in the Rapid7 Security Console, especially validate the counts and priorities.
- Control access. A bulk export can contain your whole vulnerability dataset, so limit who can run it and which AI tools can reach the data.
- Keep data private. The server and skill are open source, so you can inspect the code. Check where your chosen AI client sends prompts and data, as that depends on the client and model you use.
- Refresh the data. The local copy is a snapshot, so reload it after new scans or patching.
6. Frequently asked questions
Does Rapid7 have vulnerability checks for this CVE?
Refer to section 1, Product Coverage at a glance.
I searched my Security Console and I couldn’t find the CVE. Why?
Your console likely hasn’t received the new content yet. See Get the new content for guidance on updating and validating the content version.
I updated the content. Why don’t I see any findings?
Findings only appear after you rescan.
How do I scan for only this vulnerability?
Refer to Optional: scan for this vulnerability.
How do I find every system running Java, including ones that aren’t vulnerable?
Vulnerability Management (InsightVM)‘s software inventory can help, but it may miss Java that was built from source or bundled inside an application.
How will I be kept up to date?
This page and the ETR blog post will be updated as new information becomes available, https://www.rapid7.com/blog/post/etr-cve-2026-114938-reported-critical-pre-authentication-remote-code-execution-java-17/