Urgent.News

What's breaking now, across thousands of outlets.

Tech

Java4Shell: RCE in OpenJDK when processing Base64

A critical vulnerability has been disclosed in OpenJDK's Base64 decoder, allowing remote attackers to corrupt memory and potentially execute arbitrary code. This Java4Shell (CVE-2026-114938) issue scores 9.2 out of 10 on the CVSS scale, making it critical. OpenJDK is the most widely used Java runtime environment, powering 90% of Fortune 500 companies. Base64 is a common method of encoding binary data as text, used in various applications such as authentication and file uploads.

The vulnerability arises from an optimization in OpenJDK that uses specialized x86-64 CPU instructions for faster Base64 decoding. A bug in the optimized machine-level code allows malicious input to overwrite neighboring memory, potentially exposing sensitive information or leading to remote code execution (RCE). The exploit can be triggered by a short string of characters (64 "A"s followed by "=") in older OpenJDK 17 versions, and even older versions up to Java 11.

Applications using popular frameworks like Apache Struts and Spring Boot are also at risk, as the vulnerability can be triggered through ordinary features like authentication and file uploads. Even client-side Java programs interacting with malicious servers can be compromised, illustrating the far-reaching impact of this vulnerability.

OpenJDK's memory safety features, which are generally a strength, are undermined by this vulnerability, highlighting the complexity of maintaining memory safety across different programming languages and environments. The vulnerability was discovered using AI-assisted techniques, demonstrating how technology can aid in both discovering and mitigating such security risks.

However, the presence of unnecessary features in widely used software stacks, like the optimized Base64 decoder in OpenJDK, presents ongoing challenges in managing system attack surfaces and ensuring security.

Written by urgent.news from Lobsters's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Every outlet that reported this, and when →

Read the original at calif.io →

More in Tech

Why We Switched From Homegrown Feature Flags to LaunchDarkly (And What We Learned)

We built our own feature flag system three years ago. It started as a simple Redis hash: feature:new-checkout -> {enabled: true, percentage: 50} . A Rake task to flip it.

  • Switched from homegrown to LaunchDarkly after three years
  • Homegrown system lacked audit trail, segmentation, kill switch
  • Migration took two sprints, impacted day-to-day operations positively

A job board that agents pay for: four x402 bugs we hit before a directory would list it

We run a small job board for AI agents at agent-job-board.obtranzat.workers.dev . No accounts, no API keys: an agent pays 0.02 USDC to read the board, 0.50 to post a job, 0.01 for an aggregated feed…

  • Agents pay 0.02 USDC to read job board, 0.50 USDC to post job
  • x402 v2 rail on Base (eip155:8453) facilitates payment process
  • Multiple fixes addressed HEAD request oversight, discovery, multi-rail handling, error handling

UUID v4 or auto-increment? A practical guide to picking primary keys

Every project hits the same fork the moment you design your first table: do primary keys count up — 1, 2, 3 — or do they look like 550e8400-e29b-41d4-a716-446655440000 ?

  • Use UUID v4 when clients generate IDs, ensuring uniqueness with minimal risk of collisions.
  • UUIDs eliminate the need for round-trips to retrieve IDs and prevent business data leakage.
  • Consider UUID v7 for ordered UUIDs to maintain insert locality in clustered indexes.

Jon Tower

"CBS Mornings" executive producer

  • Jon Tower is executive producer of CBS Mornings
  • Over a decade overseeing broadcast production
  • Formerly at MSNBC, launched Morning Joe

More from Tuesday 17 November →