This week's thread is software that sits deep in the stack. A bug in Java's built-in Base64 decoder can lead to remote code execution in tools such as Jira, Jenkins and Keycloak, and a widely used Python package for building AI agents had two releases published with a credential stealer inside. An AI gateway that many teams run in front of their model providers was added to the list of attacked software.
Two planned releases land today too: a critical PHP security release and PostgreSQL 19.
Java4Shell: a Base64 bug in the JVM
On 17 November Oracle and the OpenJDK project fixed CVE-2026-114938, nicknamed Java4Shell, and CISA urged everyone to patch immediately. It is a memory corruption bug in the fast Base64 decoder of the HotSpot JVM. A short, malformed Base64 string can crash Java and, with work specific to each application, run code on the server.
According to Calif, the researchers who found it, that works without logging in against default setups of Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate, and after logging in against Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. They are holding back those exploits for now. No attacks had been reported as of 18 November, but the cause and the trigger are public.
Two conditions decide whether a machine is exposed:
- The Java version. OpenJDK 17.0.6 and later, plus 21, 25 and 27, from any vendor: Oracle, Temurin, Corretto, Zulu and the rest. Java 8 and 11 are not affected.
- The CPU. Only x86-64 processors with AVX-512 VBMI run the vulnerable code:
Intel Xeon from Ice Lake onwards and AMD Zen 4 and newer. ARM servers are not
affected. On Linux, a machine is in scope when all four of
avx512f,avx512bw,avx512vbmiandbmi2appear in/proc/cpuinfo.
The CPU check is less reassuring than it sounds. The same container image can be safe on one host and exposed on the next, and on shared cloud machines you rarely choose the processor. Treat every affected Java version as vulnerable.
| Java line | Fixed in |
|---|---|
| 27 | 27.0.1.1 |
| 25 | 25.0.5.1 |
| 21 | 21.0.13.1 |
| 17 | 17.0.21.1 |
Vendors add their own build suffix, so Eclipse Temurin's fix for 21 is 21.0.13.1+2 and Amazon Corretto's is 21.0.13.1.2. Non-LTS lines such as 22, 23, 24 and 26 get no fix and need to move to a supported version. As of 18 November, Red Hat had not yet shipped fixed builds.
What to do:
- Update Java on servers you manage, then restart every Java process.
- For a container image, rebuild on an updated base image, such as
eclipse-temurin:21, once your vendor's fixed images are published, and redeploy. Check thatjava -versionreports at least the fixed version. - Remember the Java you did not install yourself: the runtime bundled with Jira, Jenkins, Keycloak, Elasticsearch and similar products.
- If you cannot update yet, start the JVM with
-XX:-UseBASE64Intrinsics. This switches off the fast decoder and may slow down Base64-heavy work. Runjava -XX:-UseBASE64Intrinsics -versionfirst to confirm your JVM accepts it, and remove it once you are patched.
A poisoned release of Microsoft's agent-framework on PyPI
On 17 November two malicious versions of
agent-framework,
Microsoft's Python package for building AI agents, were published to PyPI:
1.26.1 at 20:35 UTC and 1.26.2 at 21:08 UTC. Both have been removed.
1.26.0 is the last clean release, and sibling packages such as
agent-framework-core were not affected.
The malware installs a .pth file, which Python runs on every interpreter
start, so it ran even in projects that never imported the framework. It
collected environment variables, cloud and registry credentials (Azure, AWS,
GitHub, Docker, npm, PyPI, Hugging Face, OpenAI) and .env files, and in
1.26.2 also requested GitHub Actions OIDC tokens. Microsoft has not yet said
how the attacker got publishing access.
What to do:
- Search lockfiles, CI caches and container images for
agent-framework1.26.1 or 1.26.2. A loose pin such as>=1.26may have pulled one in. - If you find either, the GitHub advisory says to treat the environment as exposed and rotate every credential reachable from it, including CI and GitHub Actions secrets.
- Pin to
agent-framework==1.26.0, ideally with hashes, and rebuild from a clean environment.
The wider lesson applies to any dependency: CI runners and build machines hold the most valuable secrets you have. Give each job only the tokens it needs, and prefer short-lived credentials over long-lived keys in environment variables.
LiteLLM is being attacked
On 18 November CISA added CVE-2026-40217 in LiteLLM, the open-source proxy many teams put in front of their AI model providers, to its catalogue of actively exploited vulnerabilities. The bug was fixed in the spring, so this is about installations that were never updated.
The POST /guardrails/test_custom_code endpoint ran user-supplied Python in a
home-made sandbox that could be escaped, giving code execution in the proxy
process, which runs as root in the default Docker image. Reaching it needs a
proxy admin credential in a default setup. A LiteLLM proxy typically holds API
keys for every model provider you use, so a takeover is expensive.
What to do:
- Upgrade to a current LiteLLM release. The advisory covers versions from 1.81.8 and lists the fix as landing in 1.83.10 or 1.83.11, so do not stop at the first fixed version.
- If you cannot upgrade straight away, block
POST /guardrails/test_custom_codeat your reverse proxy. - Keep the admin interface off the public internet, and rotate the master key and provider keys if an old version was exposed.
Due today: PHP and PostgreSQL 19
The PHP project has announced a critical security release for every supported PHP version today, 19 November, between 14:00 and 14:30 UTC. It says the critical issues need a non-default configuration or an uncommon setup, and fixed version numbers will be published with the release. Plan to update this week anyway, and restart every PHP process afterwards. PHP 8.6.0 is also planned for today, so 8.6 will be the newest line by the end of the day.
If you use Cosmoner web hosting, the hosting's overview shows Security update available once a patched build for your PHP version is ready.
PostgreSQL 19
is planned for general availability today too, unless a last-minute problem
delays it. It is a major version, so moving to it needs pg_upgrade or a dump
and restore, not just new binaries. Test your application against it before
you upgrade production, and expect the first minor release to follow in a few
months. For a production upgrade this month, 18 remains the safer target.