Digest · Tuesday

Security digest: November 17, 2026

4 editorial briefs, 1 known exploited (cisa kev) addition and 1 critical advisory.

All digests · RSS · Markdown

Take stock

  • Act now: Puppet CVE-2026-115731: Exploited RCE via Agent Reports. Anyone running Puppet Enterprise, Puppet Core, OpenVox Server or legacy open-source Puppet Server, and Red Hat Satellite admins using its Puppet features, most urgently where autosign is on or port 8140 is reachable from untrusted networks.
  • Act now: Java4Shell. Anyone running OpenJDK-based Java 17.0.6 or later (any vendor build) on x86-64 CPUs with AVX-512 VBMI, especially internet-facing services, identity servers and CI systems, and appliances or containers that bundle such a JRE.
  • Act now: Apache Roller CVE-2026-129448: Exploited XML-RPC RCE. Anyone running Apache Roller 4.0.0 through 6.1.5, especially instances reachable from the internet, including sites that turned XML-RPC off in the admin UI.
  • Check exposure: Microsoft agent-framework PyPI Hijack Steals CI Credentials. Anyone whose lockfiles, CI logs, caches, internal mirrors or container images show agent-framework 1.26.1 or 1.26.2, including CI runs on Renovate or Dependabot upgrade pull requests opened on November 17, 2026.
  • Do you run any of these? Perforce Puppet Enterprise. They are being exploited in the wild (CISA KEV). Patch or mitigate if you do; CISA’s federal deadline is 2026-12-01.
  • PyPI: 1 critical advisory (arize-phoenix). Check with pip-audit (or: pip show <package>).
  • None of it touches your stack? Then there is nothing to do today. That is a result, not a failure to read carefully.

Editorial briefs

Act now

· Vulnerability · CVE-2026-115731

Puppet CVE-2026-115731: Exploited RCE via Agent Reports

Patch Puppet and OpenVox servers now and turn off loose autosigning: CISA lists the flaw as exploited, a public proof of concept exists, and one compromised node is enough to take the server that controls your whole fleet.

Must act: Anyone running Puppet Enterprise, Puppet Core, OpenVox Server or legacy open-source Puppet Server, and Red Hat Satellite admins using its Puppet features, most urgently where autosign is on or port 8140 is reachable from untrusted networks.

Can relax: Organizations that do not use Puppet or OpenVox, and servers already on the fixed releases with strict certificate signing and no signs of earlier compromise.

  1. Upgrade Puppet Enterprise to 2026.0.1, 2025.12.1 or 2023.8.13, Puppet Core to 9.1.3 or 8.22.2, or OpenVox to server 9.2.0 or 8.18.0 with agent 9.3.0 or 8.32.0 on the server host.
  2. Check autosigning with puppet config print autosign --section server and disable it, or replace it with policy-based signing that verifies each request.
  3. Allow port 8140 on the server only from networks where managed nodes actually live.

Read the brief →

Act now

· Vulnerability · CVE-2026-114938

Java4Shell: OpenJDK Base64 Heap Overflow Enables RCE

If you run Java 17 or later on recent Intel or AMD servers, patch today or set -XX:-UseBASE64Intrinsics now: the bug is trivial to trigger, researchers showed pre-auth RCE in default Jenkins, Jira, Confluence and Keycloak, and full exploits already circulate privately.

Must act: Anyone running OpenJDK-based Java 17.0.6 or later (any vendor build) on x86-64 CPUs with AVX-512 VBMI, especially internet-facing services, identity servers and CI systems, and appliances or containers that bundle such a JRE.

Can relax: Java 8 and Java 11 users (except Oracle's 8u Performance Pack), and JVMs on ARM64 or on x86-64 CPUs that lack the avx512vbmi flag; patch on your normal cycle anyway.

  1. Inventory every Java 17+ runtime, including JREs bundled in vendor apps, appliances and container images, and note which hosts have AVX-512 VBMI CPUs.
  2. Upgrade to 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1 from your JDK vendor or distribution, then restart every JVM.
  3. Where you cannot patch today, start the JVM with -XX:-UseBASE64Intrinsics (for example via JAVA_TOOL_OPTIONS) and restart it.

Read the brief →

Check exposure

· Supply-chain compromise

Microsoft agent-framework PyPI Hijack Steals CI Credentials

The bad versions were live for about 40 minutes and are now quarantined, so most teams only need to confirm they never resolved them, but any host or CI job that installed 1.26.1 or 1.26.2 must be treated as fully compromised.

Must act: Anyone whose lockfiles, CI logs, caches, internal mirrors or container images show agent-framework 1.26.1 or 1.26.2, including CI runs on Renovate or Dependabot upgrade pull requests opened on November 17, 2026.

Can relax: Projects pinned to 1.26.0 or earlier, and anything that did not resolve a fresh agent-framework version between 20:35 and 21:16 UTC on November 17, 2026.

  1. Search lockfiles, CI logs, dependency caches, internal mirrors and container images for agent-framework 1.26.1 or 1.26.2.
  2. If either was installed, isolate the host or runner before starting Python or pip there again, because every interpreter start re-runs the hook.
  3. Rebuild affected machines, runners and images from a clean base and pin agent-framework==1.26.0 with hashes.

Read the brief →

Act now

· Vulnerability · CVE-2026-129448, CVE-2026-82384

Apache Roller CVE-2026-129448: Exploited XML-RPC RCE

If you run Apache Roller, upgrade or disable the XML-RPC extension setting today: one unauthenticated POST runs code, Apache says attacks are under way, and September's advisory understated which versions were vulnerable.

Must act: Anyone running Apache Roller 4.0.0 through 6.1.5, especially instances reachable from the internet, including sites that turned XML-RPC off in the admin UI.

Can relax: Organizations that do not run Apache Roller and instances already on 6.1.6 or 6.1.7 that show no signs of earlier compromise.

  1. Upgrade every Apache Roller instance to 6.1.7 (6.1.6 at minimum) and restart the servlet container.
  2. If you cannot upgrade today, set enabledForExtensions to false on XmlRpcServlet in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, then restart; the admin UI toggle is not enough.
  3. Block /roller-services/xmlrpc at the reverse proxy or WAF unless you rely on XML-RPC blogging clients.

Read the brief →

Known exploited (CISA KEV) 1

Added to CISA’s catalog on this day: confirmed exploitation in the wild. Due date = CISA’s deadline for US federal agencies.

CVEProduct and flawCISA due
CVE-2026-115731Perforce Puppet Enterprise
Perforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability
2026-12-01

Critical advisories by ecosystem 1

GitHub-reviewed advisories rated critical, published this day (Pacific time).

PyPI 1

Check: pip-audit (or: pip show <package>)