Java Vulnerability Assessment and Remediation on AWS by Firemind

Find every Java runtime in your AWS estate. Fix it. Keep it fixed.

Firemind’s IT Operations Engine finds every place Java runs, including the bundled JDKs operating-system patching misses, fixes it under your change rules, checks the build actually running, and keeps checking so an exposed version doesn’t come back.

Days
to the first report after you connect
Your rules
high-risk fixes wait for your approver
Logged
every action, in your AWS CloudTrail
Keep green
continuous checks for the term you choose

Current advisory: Java4Shell

Java4Shell (CVE-2026-114938), also reported as Java2Shell, is a flaw in the OpenJDK Base64 decoder that lets crafted input corrupt memory, often before login; researchers showed code execution on default installs of Keycloak, Jira, Jenkins and others. It affects OpenJDK-based runtimes from 17.0.6, including 21, 25 and 27, but only on x86-64 processors with AVX-512 VBMI (Intel Ice Lake and later, AMD Zen 4 and later). Graviton isn’t affected. Fixed builds include Amazon Corretto 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2 and 27.0.1.1.4; the JVM flag -XX:-UseBASE64Intrinsics is the interim mitigation.

Connect, find, fix, keep green.

1 · Connect

Accept the offer, deploy one role.

After you accept the private offer, deploy an IAM role with AWS CloudFormation. The Engine works through the AWS API with temporary credentials.

2 · Find

The first report within days.

An inventory of every Java runtime with its vendor, build, exposure and fix status, from EC2 metadata, Systems Manager Inventory, Amazon Inspector, image metadata and your repositories, each checked against its processor.

3 · Fix

Fixed under your change rules.

Runtime updates through Patch Manager, JDK and base-image pull requests, image rebuilds, Lambda runtime updates and interim JVM flags, with the running build checked after each fix. Production restarts wait for your approver.

4 · Keep green

It stays fixed.

Continuous checks run for the term you choose, so a new instance, image or function can’t quietly reintroduce the exposure.

Where it looks, and how it fixes

Start with the free assessment →

  • Amazon EC2, container images in Amazon ECR on ECS, EKS and Fargate, Lambda and Elastic Beanstalk Java environments
  • The copies operating-system patching misses: JDKs bundled in container images, Lambda container images, vendor products and Marketplace appliances
  • A processor check per workload: affected instance types first, Graviton confirmed clear, resize risk flagged
  • Runtime updates through Systems Manager Patch Manager, image rebuilds through your pipelines and base-image pull requests your engineers review
  • Interim JVM-flag mitigations where an update has to wait, plus secret rotation where you choose
  • Continuous checks that new instances, images and functions ship fixed builds, and that interim flags come off once fixed

Whatever happens, you're no worse off.

We designed this so there is no outcome where you lose. Here is every way it can go.

If this happensThen this is where you stand
You read the first report and stop.You keep the inventory of every affected Java runtime, with its exposure and the proposed fix. Remove the role and access ends.
A fix needs a production restart.It waits for your named approver. Low-risk, reversible fixes run automatically; everything is logged in CloudTrail.
A fix doesn’t hold.Keep-green checks catch the drift and fix it again under the same rules, for the term you chose.
A new deployment ships the old version.Continuous checks flag it before it becomes the next exposure, and it’s fixed under the same rules.
The next advisory lands.Same listing, same access, same rules. We point the Engine at the new exposure; nothing new to procure.

Done before

~90%
of incidents auto-resolved before anyone is paged, in production
9 min
average time to resolution, from detection to verified fix
~24x
less effort across 36 tests, zero disruptions, for a Nordic enterprise (non-production pilot)
$350,000
annual AWS savings identified for an automotive services group
“I've started this initiative five times and never succeeded.”
Cloud Center of Excellence Lead, Nordic enterprise

The Engine finished that tagging compliance initiative in under nine minutes.

Firemind is ISO 27001:2022 certified. AWS, NVIDIA and Anthropic partner.

One role, temporary credentials. High-risk changes wait for a person.

The Engine works through the AWS API. What it may do on its own and what needs a named approver is agreed with your team before anything runs.

Connect
An IAM role you deploy with CloudFormation
Credentials
Temporary, through the AWS API
Low-risk fixes
Reversible, run automatically, logged
High-risk fixes
Wait for your named approver
Audit
Every action in your AWS CloudTrail

Why through AWS Marketplace

Available in AWS Marketplace

On your AWS invoice

Billed through your existing AWS account, alongside everything else you run.

AWS’s standard terms

Procured on AWS Marketplace’s standard terms, so procurement has seen them before.

No new supplier

Nothing new to set up as a supplier. Accept the private offer and start.

Request a private offer on AWS Marketplace →

Prefer to talk first, or not on AWS yet?

Fill this in and a Firemind engineer replies the next working day. We'll talk through your estate and what the engagement would cover, then you decide whether to go ahead on AWS Marketplace.

We only use this to reply about Java vulnerability. No newsletter, no sales call unless you ask for one.Privacy Policy.