Skip to content
Tityra
Login
Start for free
HomeAboutWho It's For
  • Publishers & Media
  • Ecommerce & Retail
  • SaaS & Technology
  • Agencies
  • Government & Public Sector
  • Financial Services & Insurance
PricingFAQBlog
info@tityra.com
XLinkedIn
  1. Home
  2. /
  3. Blog
  4. /
  5. Web operations

Java4Shell (CVE-2026-114938):
What website teams should check

Find out when Java4Shell can affect a website or API, who owns the Java update and how to verify the build in production.

5 min read

Doğu Abaris · 18 November 2026

Read the article

Used by many

  • Onedio
  • Maçkolik
  • Webtekno
  • Yemek.com
  • Mynet
5/51 review on G2
Start for free

UNDERSTAND CONTENT DELIVERY

Learn what a tested client receives.

FOLLOW THE EVIDENCE

See how observations become findings.

PUT GUIDANCE INTO PRACTICE

Find changes your team can investigate.

Read the article

In this article

What is Java4Shell?When can a website be affected?Find the Java build each service runsChoose the update for that deploymentVerify the running updateWhat to record before closing the ticket
How we audit
Table of Contents
What is Java4Shell?When can a website be affected?Find the Java build each service runsChoose the update for that deploymentVerify the running updateWhat to record before closing the ticket
How we audit

Java4Shell can affect a website through a vulnerable Java runtime behind it. Check the services your site depends on, including separately hosted APIs and sign-in services.

Copy linkWhat is Java4Shell?

Java4Shell is the name given to CVE-2026-114938, a memory corruption flaw in certain Java runtime builds. On affected deployments, code could run remotely without a login. Oracle assigned the flaw a CVSS v3.1 base score of 8.1 and addressed it in its 17 November 2026 security update. See Oracle's November 2026 security advisory.

Calif researcher Quang Luong discovered the flaw, and Calif disclosed Java4Shell on 17 November 2026. The disclosure is listed in Calif's research index. Oracle's credit statement names Quang Luong of Calif and Albert Yang as reporters of the same CVE.

The flaw is in an optimised Base64 decoder in the Java Virtual Machine (JVM), the software that runs Java code. Red Hat identifies x86-64 processors with AVX-512 VBMI support as part of the affected setup. Exposure also depends on whether untrusted input reaches the affected decoder. See Red Hat's security bulletin.

Copy linkWhen can a website be affected?

A web application or an API can bring network input to an affected JVM. Oracle lists a web service as one example and identifies multiple protocols in its risk matrix. This makes the runtime behind a site relevant, including services outside the path that serves its pages. See the Oracle Java risk matrix.

Take a static site that serves HTML, CSS and JavaScript from a content delivery network. The network serves the files and the browser runs the JavaScript. If the site depends on a separately hosted Java API or sign-in service, check that service's runtime, host and update owner. Inspecting the public page alone can't tell you which Java build those services run.

The distinction matters in real products. Atlassian's mitigation notice lists Jira and Confluence Data Center among affected products in standard installations. When we checked it on 18 November 2026, Atlassian said it was still investigating Cloud impact and asked Cloud customers to take no action at that point. See Atlassian's Data Center notice.

Hosting arrangements matter as well. Google Cloud separates its managed Kubernetes control plane from Java running in customer containers. Its bulletin also covers Java workers for Dataproc and Dataflow, which can run without serving a website. Check the instructions for your service and for the way its runtime is supplied. See Google Cloud bulletin GCP-2026-082.

Copy linkFind the Java build each service runs

Start with the service that runs in production. A shell's java -version reports the Java executable selected by that shell. The web service may start through a different path, a container image or a copy of Java supplied with the application.

Use the service's startup logs or supported diagnostics to find the version. Where jcmd is available, run jcmd 1234 VM.version using the service's actual process ID in place of 1234. Run the check on the same machine as the JVM with the same effective user and group as the service. For a container, use the deployment's supported diagnostic access and the process ID visible from that environment. See Oracle's jcmd reference.

Start with services reachable from the internet. Record the application, environment, Java vendor and full build, the CPU features visible to the workload and who owns the update. If a product bundles Java, also record its product release. For services you don't operate, check the provider's product advisory or ask it to confirm the update.

Copy linkChoose the update for that deployment

Use the bulletin for the distribution and full build you identified. Oracle's affected list includes a specific Java 8 performance build, 8u511b33-perf. Broad statements about Java major versions can miss builds like this one. See Oracle's Java SE risk matrix.

On the Oracle JDK 17 line, Oracle lists 17.0.21.0.3 as affected and documents 17.0.21.1+4 as the 17 November security update in its JDK 17 release notes. For Corretto 17 on Amazon Linux 2023, the updated RPM uses the package version 17.0.21.1.2-1.amzn2023.1. Compare package versions with the package bulletin and runtime builds with the runtime release notes. See Amazon Linux advisory ALAS2023-2026-3478.

Apply the supported update, then restart or replace the service so it starts with the corrected runtime. If the vendor supplies a bundled JVM, follow its product update instructions. For a container build, update the Java used in the final image, rebuild it and roll it out to every replica. See Docker's build guidance on rebuilding images.

If your supplier hasn't released a fix for your build, follow any temporary mitigations it recommends. Assign an owner to track the advisory and apply the update when it becomes available.

Copy linkVerify the running update

Check the Java build reported by the restarted service and compare it with the vendor's fixed release. If you rolled out a container, confirm that every running replica uses the new image and check the runtime from that deployment. Run the usual health checks and record the evidence in the update ticket.

For example, imagine a web application running in two containers. The team updates Java on the host, but both containers still report the old build. They rebuild the application image with the vendor's fixed Java and replace both containers. The update ticket records the new image identifier and the Java build reported by the running service.

Copy linkWhat to record before closing the ticket

Keep enough evidence for another team member to verify the update.

  • The affected service and environment, the Java vendor and build, and who owns the update.
  • The applicable vendor bulletin and the corrected package, product release or image.
  • Evidence that the service was restarted or replaced and now runs the corrected build.
  • Health check results and the owner of any deployment that still needs an update.

Copy linkSources and further reading

  1. Calif research index, including the 17 November 2026 Java4Shell disclosure
  2. Oracle November 2026 security advisory and Java risk matrix
  3. Red Hat OpenJDK security bulletin RHSB-2026-018
  4. Atlassian guidance for affected Data Center products
  5. Google Cloud bulletin GCP-2026-082 on Java workloads
  6. Oracle JDK 17.0.21.1 release notes
  7. Amazon Linux 2023 Corretto 17 advisory ALAS2023-2026-3478
  8. Oracle jcmd diagnostic command reference
  9. Docker guidance on rebuilding images with updated dependencies
Doğu Abaris

About the author

Doğu Abaris

Doğu Abaris is a software and data engineer and a co-founder of Tityra. For more than a decade, he has built maintainable software for production, working across front-end and back-end development. He also contributes to open-source software and web standards.

More about Doğu

Check the advisory for your Java build

Use the affected versions and patch information for the product and distribution your service runs.

Read Oracle's Java advisory
Share this article

Share this article

Keep exploring

Content access

Why AI crawlers are blocked by Cloudflare

Check why an AI crawler receives a Cloudflare block or challenge, find the rule involved and verify access to the public content you intend to share.

Read article

Content access

Why AI crawlers may miss JavaScript-rendered content

Your browser can show a complete page while another client receives only a loading message. Here's how to check where the content appears.

Audit practice

What is a content audit?

Learn how a content audit helps you decide what to change on your website, with a practical review process, an illustrative example and a checklist you can use.

Turn findings into
clear next steps.

Start for free
BlogAudit methodologyAPI docsMCP docsCLIGitHubContact

TITYRA LTD

120 Main Street
Largs, Scotland, KA30 8JN
info@tityra.com
HomeAbout
Who It's For
  • Publishers & Media
  • Ecommerce & Retail
  • SaaS & Technology
  • Agencies
  • Government & Public Sector
  • Financial Services & Insurance
PricingFAQ

© 2026 TITYRA LTD. All rights reserved. Registered in Scotland, company SC908253.

PrivacyTerms and ConditionsCookie informationCookie preferences

We value your privacy

By clicking "Accept all cookies", you agree to the storing of optional analytics cookies on your device to help us understand site usage and improve our website. You may click the customise button to choose which optional cookies you would like to allow.

Strictly necessary (2)

We save your cookie choice in this browser for six months, so you don't have to choose on every visit. This storage is always on.

Show detailsHide details for strictly necessary
  • Name
    tityra_analytics_consent_v1
    Provider
    Tityra (tityra.com)
    Type
    HTML local storage
    Maximum storage duration
    Persistent

    Remembers whether you accepted or rejected analytics. Your choice is valid for 180 days (six months), after which we ask again. The stored record remains until it is replaced or you clear your browser storage.

  • Name
    tityra_analytics_consent_v1_refusal
    Provider
    Tityra (tityra.com)
    Type
    HTML session storage
    Maximum storage duration
    Browser tab session

    Keeps analytics off if your browser can't save a rejection in local storage. This fallback is only used when needed and is cleared when a subsequent choice is successfully saved.

Google Analytics helps us understand page visits, content engagement, interest in audit packages and account signup link clicks. It only loads after you accept. Advertising features are disabled.

Show detailsHide details for analytics
  • Name
    _ga
    Provider
    Google Analytics (tityra.com)
    Type
    HTTP cookie
    Maximum storage duration
    Up to 180 days (six months)

    Distinguishes visitors to help us understand how the website is used. Set only after you accept analytics; advertising features are disabled.

  • Name
    _ga_*
    Provider
    Google Analytics (tityra.com)
    Type
    HTTP cookie
    Maximum storage duration
    Up to 180 days (six months)

    Maintains analytics session information, such as visits and interactions with the website. Set only after you accept analytics. The asterisk represents the identifier in the cookie name.

You control whether optional analytics runs on this website. We remember your choice for six months, and you can change it at any time using Cookie preferences in the footer.

Rejecting or withdrawing consent stops analytics and removes the Google Analytics cookies this website can access.

The details list the name, provider, purpose, type and storage duration of each entry. Contact details and private account information aren't included in website analytics.

Counts describe the entries listed, including the fallback and cookie name pattern, rather than cookies currently stored on your device.

Read our cookie information