/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Cybersecurity startup Calif says it used GPT-6 Cyber to uncover an RCE flaw in Java dubbed “Java4Shell” and coordinated with Five Eyes; Oracle released a patch

The discovery by security company Calif shows A.I.'s ability to find gaping security holes in popular software.

New York Times

Context & Ripple Effects

Java’s security history includes sandbox-bypass flaws in 2012 and multiple Java 7 zero-days in 2013, which prompted an emergency Oracle security update. Calif’s disclosure puts a newly patched remote-code-execution issue into that lineage, but adds an important operational detail: a cybersecurity startup says an AI system helped find it.

OpenAI had already said GPT-6 Cyber outperformed GPT-6 Astra on cyber benchmarks and vulnerability discovery. The Java finding is a concrete test of whether such tools increase defensive discovery fast enough for vendors and software operators to absorb the resulting remediation work.

First-order effects

  • Oracle’s patch gives Java operators a remediation path, while Calif’s disclosure requires them to identify affected deployments and apply the update.
  • Calif gains evidence that GPT-6 Cyber can contribute to finding severe flaws in widely deployed software, not only to benchmark performance.

Second-order effects

  • Enterprise security teams and Java vendors face a faster triage cycle as AI-assisted discovery produces findings that still require patch validation, deployment, and exposure assessment.
  • Oracle’s response will be judged not only on the patch itself but on how clearly it helps customers determine whether their Java configurations are affected.

Third-order effects

  • If AI lowers the cost of finding high-severity bugs, the constraint in application security shifts further from discovery to coordinated remediation across software suppliers and their customers.
  • The same code-intelligence capabilities raise the value of defensive AI parity: defenders need automated validation and patch rollout to keep pace with automated vulnerability research.

The trend: AI-assisted vulnerability research is pushing software security toward a machine-speed contest between flaw discovery and coordinated remediation.

Discussion

  • @watchtowrcyber @watchtowrcyber on x
    watchTowr continues to track “Java4Shell” (CVE-2026-114938) now that public writeups and advisories have been released. Specific CPU, JDK, and Base64 pre-reqs are required. It's likely application-specific exploits will be developed, rather than indiscriminate exploitation.
  • @hopefullysc @hopefullysc on x
    The joy just keeps coming .. and coming... and coming. Something used by the vast majority of Fortune 500 companies https://www.cisa.gov/... [image]
  • @roddux @roddux on x
    Resources for this suggest it's a bug in Base64 handling on a hot path, with AVX512 doing something wrong, leading to memcorruption. This leads me to guess you may be able to mitigate this by disabling AVX512 on your Java boxes... Time will tell. Nice bug!
  • @0rshemesh_ Or Shemesh on x
    1/n That new “Java4Shell” bug (CVE-2026-114938). A memory corruption “RCE” in OpenJDK's Base64 decoder. Java is memory-safe, so how? https://github.com/...
  • @jeremiahg Jeremiah Grossman on x
    “One thing to note about this vulnerability is that there is no universal exploit.” whew!
  • @gdb Greg Brockman on x
    GPT-6 Cyber for helping further secure the internet, with a major security flaw in Java found by Calif, as part of our Patch the Planet initiative: https://www.nytimes.com/...
  • @vxdb @vxdb on x
    RCE Found in Java Researchers at @calif_io discovered a memory corruption vulnerability in OpenJDK's Base64 decoder allowing attackers to gain RCE on a number of Java apps in their default configs. https://calif.io/... tl;dr world is ending
  • @magmill95 Maggie Miller on x
    Because today's news cycle is so calm, CISA is telling organizations to implement a patch for the newly disclosed Java4Shell vulnerability immediately. This is a vulnerability in one of the world's most popular programming languages: https://www.cisa.gov/...
  • @cisacyber @cisacyber on x
    🚨We urge orgs to immediately patch the recently disclosed Oracle Java vuln CVE-2026-114938. This critical memory-corruption vulnerability, known as “Java4Shell,” affects the Base64 decoder of the x86-64 HotSpot JVM, part of the Java Development Kit. 🔗https://go.dhs.gov/5CC
  • @calif_io @calif_io on x
    Since the vulnerability has leaked: Calif discovered and reported Java4Shell (CVE-2026-114938). We're publishing technical details by 1 PM Pacific today, after Oracle releases a patch. Stay tuned!
  • @lcamtuf @lcamtuf on x
    I hope you guys weren't using Java for anything important
  • @calif_io @calif_io on x
    Java4Shell: write once, RCE everywhere https://calif.io/...
  • @dylfreed Dylan Freedman on x
    @dnvolz @calif_io I verified the bug myself with guidance from @calif_io in under an hour. And got to use the term “heap grooming” — a first for The New York Times.
  • Matthew Wilson Matthew Wilson on linkedin
    #java4shell is not #log4shell.  —  With log4shell, the exploit was a single shot where an attacker didn't even have to aim.  That's not what java4shell looks like. …
  • @doublepulsar.com Kevin Beaumont on bluesky
    Don't panic about this.  It needs a very specific config to be actually exploitable.  It will not get much real world exploitation.  —  It's a valid vuln but - for example - there was an unauth RCE in last thr OpenJDK release, too.  Vulns happen.  This one will get AI hype market…
  • @ericjgeller.com Eric Geller on bluesky
    CISA urges organizations to immediately patch Java4Shell: www.cisa.gov/news-events/...
  • r/java r on reddit
    Java RCE CVE-2026-114938
  • r/antiai r on reddit
    BREAKING: Everything |  Flights?  Banks?  Microsoft?
  • r/Anticonsumption r on reddit
    BREAKING: Everything
  • r/programming r on reddit
    Java4Shell: RCE in OpenJDK Base64 (Calif)
  • r/technology r on reddit
    Critical flaw found in vital internet platform Java through AI
  • @cyb3rops Florian Roth on x
    CVE-2026-114938 Java4Shell Write once, RCE everywhere A memory-corruption vulnerability in OpenJDK's Base64 decoder. A remote attacker with no credentials can overwrite heap memory, read it in the style of Heartbleed, and reach remote code execution. https://calif.io/...
  • r/Economics r on reddit
    BREAKING: Everything
  • r/pwnhub r on reddit
    Everything Is Breaking: Why Apple Pay, banks, and airplanes are suddenly crashing all at once.
  • @doctorow.pluralistic.net @doctorow.pluralistic.net on bluesky
    Corporate management has spent decades playing IT Jenga, removing every available block, leaving behind a skeletal skyline of teetering towers that now routinely collapse:  —  https://www.404media.co/breaking- everything/
  • r/hacking r on reddit
    Java4Shell Write once, RCE everywhere
  • r/netsec r on reddit
    Java4Shell: Write once, RCE everywhere