Cyber Threat Brief — November 18 2026
1. Puppet Server report deserialization
TL;DR: CISA added CVE-2026-115731 to KEV on 17 Nov with a federal due date of 1 Dec. Install the fixed Puppet Enterprise or Puppet Core build for your train and restart Puppet Server.
What’s New:
- CISA lists CVE-2026-115731 as exploited in the wild. A client that already holds any CA-signed agent certificate can PUT a report with a crafted rich-data type and run code as the Puppet Server user. If the CA autosigns certificates without a strong check, that first certificate does not require prior access. Federal agencies have until 1 Dec. CISA alert, KEV catalog.
- Puppet says Puppet Enterprise 2026.0.1, 2025.12.1, and 2023.8.13, and Puppet Core 9.1.3 and 8.22.1, fix CVE-2026-115731 (report deserialization) and CVE-2026-115732 (a certificate-name check that let a partial name impersonate another machine). Puppet what’s new.
- Vox Pupuli says every known Puppet implementation was affected, that open-source Puppet will not receive further security updates, and that openvox-server 8.18.0 and 9.2.0 contain the fix. The report endpoint is
PUT /puppet/v3/report. Vox Pupuli, OpenVox advisory. - The Hacker News restates the CISA description. It is not a second origin. The Hacker News.
Actionable Intel
| Artifact | Type | ATT&CK | Log Source | Action |
|---|---|---|---|---|
| Puppet Enterprise 2026.0.1 | Fixed build | T1190 | Puppet Server version | Install Puppet Enterprise 2026.0.1 on the 2026 train and restart the Puppet Server service. |
| Puppet Enterprise 2025.12.1 | Fixed build | T1190 | Puppet Server version | Install Puppet Enterprise 2025.12.1 on the 2025 train and restart the Puppet Server service. |
| Puppet Enterprise 2023.8.13 | Fixed build | T1190 | Puppet Server version | Install Puppet Enterprise 2023.8.13 on the 2023 train and restart the Puppet Server service. |
| Puppet Core 9.1.3 | Fixed build | T1190 | Puppet Server version | Install Puppet Core 9.1.3 on the 9.x train and restart the Puppet Server service. |
| Puppet Core 8.22.1 | Fixed build | T1190 | Puppet Server version | Install Puppet Core 8.22.1 on the 8.x train and restart the Puppet Server service. |
| openvox-server 8.18.0 | Fixed build | T1190 | package inventory | Install openvox-server 8.18.0 on the OpenVox 8 train and restart the server. |
| openvox-server 9.2.0 | Fixed build | T1190 | package inventory | Install openvox-server 9.2.0 on the OpenVox 9 train and restart the server. |
| open-source Puppet Server | No fixed release | T1190 | package inventory | Plan a move to OpenVox or Puppet Core. Vox Pupuli says open-source Puppet will not get further security updates. |
PUT /puppet/v3/report | Request path | T1190 | Puppet Server access log | Search for PUT /puppet/v3/report from a certname that is new, unexpected, or not in the node inventory. |
autosign = true | Config | T1078 | puppet.conf | Find autosign = true and replace it with a narrow policy before the server is reachable from untrusted networks. |
| autosign.conf | Config | T1078 | autosign.conf | Review autosign.conf for a glob that signs any CSR, and check the CA for certificates issued to names you did not expect. |
| child of the puppetserver JVM | Process behavior | T1059 | process creation | List child processes whose parent is the puppetserver Java process and investigate any shell, curl, or python child. |
Detection
| Source | Rule | Gap |
|---|---|---|
| Splunk ESCU | None — verified | Matches sudo puppet apply -e exec, not a report PUT. |
| Elastic | None — verified | Needs a public-IP java flow, -jar, and a shell within 5s. |
| Sigma | Partial — Suspicious Java Children Processes | Parent /java with a shell, curl, wget, or python child. |
Hunt hint: Read the Puppet Server access log for PUT /puppet/v3/report and group the hits by certname. Compare those certnames with the node inventory and with CSR signings from the last two weeks. Open puppet.conf and autosign.conf and flag autosign = true or a glob that signs every request. On the Puppet Server host, list children of the puppetserver JVM and keep any shell, curl, or python child. After the upgrade, restart the service and confirm the running build is the row for that train. If you find a suspicious report PUT or JVM child, treat the CA key on that server as exposed and plan to reissue agent certificates.
Sources: CISA alert, KEV catalog, Puppet what’s new, Vox Pupuli, OpenVox advisory, The Hacker News.
2. Compromised agent-framework on PyPI
TL;DR: Wiz reports that agent-framework 1.26.1 and 1.26.2 on PyPI carried a credential stealer, and the publishing path is not confirmed. Remove those two versions and rotate Azure, Azure DevOps, and GitHub Actions secrets the host could read.
What’s New:
- Wiz says 1.26.1 was published at 20:35 UTC on 17 Nov and 1.26.2 at 21:08 UTC, and that both were gone from PyPI by about 21:30 UTC. Wiz says the publishing path is not confirmed: there is no
python-1.26.1tag inmicrosoft/agent-framework, and 1.26.1 is a wheel that still depends on agent-framework-core 1.26.0. Wiz, Wiz on X. - Wiz says 1.26.1 drops
agent_framework_meta.pth, which imports code that forks and POSTs zlib-compressed credentials towebhook.site/d381fd80-ec62-42ad-8f5c-d1b15103c9bb. 1.26.2 moves the hook toaf_runtime_diag.pthand also requests GitHub Actions OIDC tokens. The marker is_AF_TEL. Wiz. - JFrog says the same two versions install a
.pthhook that steals Azure, Azure DevOps, and GitHub Actions secrets on every Python start, and says to pin 1.26.0. JFrog. - OSV MAL-2026-20101 describes the same files, the same webhook URL, and the marker
_AF_TEL. The Hacker News restates Wiz, Socket, and other labs and is not an extra origin. OSV, The Hacker News.
Actionable Intel
| Artifact | Type | ATT&CK | Log Source | Action |
|---|---|---|---|---|
| agent-framework 1.26.1 | Malicious release | T1195.001 | lockfile | Remove agent-framework 1.26.1 from the environment and from any lockfile that pins it. |
| agent-framework 1.26.2 | Malicious release | T1195.001 | lockfile | Remove agent-framework 1.26.2 from the environment and from any lockfile that pins it. |
| agent_framework_meta.pth | Startup hook | T1546.018 | file creation | Find agent_framework_meta.pth under site-packages and quarantine the directory. |
| af_runtime_diag.pth | Startup hook | T1546.018 | file creation | Find af_runtime_diag.pth under site-packages and quarantine the directory. |
| webhook.site/d381fd80-ec62-42ad-8f5c-d1b15103c9bb | Exfil URL | T1041 | proxy log | Search proxy and DNS logs for webhook.site and that UUID, then rotate Azure, Azure DevOps, and GitHub Actions secrets the host could read. |
_AF_TEL | Env marker | N/A | process environment | Search Python process environments for _AF_TEL set to 1. |
| d27fa34414e6201d5e03e559ef634f020057554d7b3f4898dd5d7cd3e989e110 | SHA256 | T1195.001 | file hash | Match this SHA256 to agent_framework-1.26.1-py3-none-any.whl and quarantine the file. |
| 3d20a8bc91351a9a16b6db243b848ceca0206b7a8623b02d2af553a9c9f7e0a9 | SHA256 | T1195.001 | file hash | Match this SHA256 to agent_framework-1.26.2-py3-none-any.whl and quarantine the file. |
Detection
| Source | Rule | Gap |
|---|---|---|
| Splunk ESCU | Partial — Python PTH File Creation During Package Installation | Windows python.exe only; needs an install and a .pth on one PID. |
| Elastic | Partial — Python Path File (pth) Creation | Linux site-packages only; no Windows or macOS .pth writes. |
| Sigma | None — verified | No SigmaHQ rule flags a new .pth file in site-packages. |
Hunt hint: Search lockfiles and installed distributions for agent-framework==1.26.1 and agent-framework==1.26.2. On each hit, look for agent_framework_meta.pth and af_runtime_diag.pth under site-packages. Search proxy logs for webhook.site and the UUID d381fd80-ec62-42ad-8f5c-d1b15103c9bb. On the same hosts, look for Python reading /proc/*/environ, ~/.azure, or GitHub Actions token variables. Rotate Azure, Azure DevOps, and GitHub Actions credentials that a poisoned host could see. Wiz and JFrog both say the last clean publish is 1.26.0; no Microsoft security advisory was posted as of this brief.
Sources: Wiz, Wiz on X, JFrog, OSV MAL-2026-20101, The Hacker News.
3. Java4Shell in OpenJDK
TL;DR: Talos reports exploitation of CVE-2026-114938 is unconfirmed. Install the November 2026 Temurin build for your train, or the Oracle Java SE CPU, and set -XX:-UseBASE64Intrinsics until that build is running.
What’s New:
- OpenJDK’s 17 Nov advisory lists CVE-2026-114938 in hotspot/compiler at CVSS 3.1 8.1, with the matrix marked for trains 17, 21, 25, and 27 and blank for 8 and 11. Oracle’s November CPU lists affected builds 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, and 27.0.1.0.3, plus GraalVM builds on the same trains. OpenJDK, Oracle CPU.
- Adoptium says Temurin builds 17.0.21.1+2, 21.0.13.1+2, 25.0.5.1+2, and 27.0.1.1+4 contain the fix, and names
-XX:-UseBASE64Intrinsicsas the interim flag. Adoptium says JDK 11 and JDK 8 are not affected. Adoptium. - Talos says the bug is in OpenJDK 17.0.6 and later when the CPU has AVX-512 VBMI, that malformed Base64 input can trigger it, and Talos reports no exploitation has been observed. Talos.
- The Hacker News says Calif demonstrated the bug against Jira, Jenkins, and Keycloak and is holding the attack code. That is a researcher claim about lab tests, and exploitation is unconfirmed. The Hacker News.
Actionable Intel
| Artifact | Type | ATT&CK | Log Source | Action |
|---|---|---|---|---|
| Oracle Java SE 17.0.21.0.3 | Vulnerable version | T1190 | java -version | Apply the 17 November 2026 Oracle Java SE Critical Security Patch Update for Oracle Java SE 17.0.21.0.3 and earlier builds on that train. |
| Oracle Java SE 21.0.13.0.3 | Vulnerable version | T1190 | java -version | Apply the 17 November 2026 Oracle Java SE Critical Security Patch Update for Oracle Java SE 21.0.13.0.3 and earlier builds on that train. |
| Oracle Java SE 25.0.5.0.3 | Vulnerable version | T1190 | java -version | Apply the 17 November 2026 Oracle Java SE Critical Security Patch Update for Oracle Java SE 25.0.5.0.3 and earlier builds on that train. |
| Oracle Java SE 27.0.1.0.3 | Vulnerable version | T1190 | java -version | Apply the 17 November 2026 Oracle Java SE Critical Security Patch Update for Oracle Java SE 27.0.1.0.3 and earlier builds on that train. |
| Oracle Java SE 8u511b33-perf | Vulnerable version | T1190 | java -version | Apply the 17 November 2026 Oracle Java SE Critical Security Patch Update for Oracle Java SE 8u511b33-perf. |
| Oracle GraalVM for JDK 17.0.21.0.3 | Vulnerable version | T1190 | java -version | Apply the 17 November 2026 Oracle Critical Security Patch Update for Oracle GraalVM for JDK 17.0.21.0.3. |
| Oracle GraalVM for JDK 21.0.13.0.3 | Vulnerable version | T1190 | java -version | Apply the 17 November 2026 Oracle Critical Security Patch Update for Oracle GraalVM for JDK 21.0.13.0.3. |
| Oracle GraalVM Enterprise Edition 21.3.20.0.3 | Vulnerable version | T1190 | java -version | Apply the 17 November 2026 Oracle Critical Security Patch Update for Oracle GraalVM Enterprise Edition 21.3.20.0.3. |
| Eclipse Temurin 17.0.21.1+2 | Fixed build | T1190 | java -version | Install Eclipse Temurin 17.0.21.1+2 on the 17 train and restart the JVM. |
| Eclipse Temurin 21.0.13.1+2 | Fixed build | T1190 | java -version | Install Eclipse Temurin 21.0.13.1+2 on the 21 train and restart the JVM. |
| Eclipse Temurin 25.0.5.1+2 | Fixed build | T1190 | java -version | Install Eclipse Temurin 25.0.5.1+2 on the 25 train and restart the JVM. |
| Eclipse Temurin 27.0.1.1+4 | Fixed build | T1190 | java -version | Install Eclipse Temurin 27.0.1.1+4 on the 27 train and restart the JVM. |
-XX:-UseBASE64Intrinsics | JVM flag | T1190 | process command line | Add -XX:-UseBASE64Intrinsics on hosts that still run an affected build, including through JAVA_TOOL_OPTIONS. |
| avx512vbmi | CPU flag | T1190 | /proc/cpuinfo | Treat a Linux host as in scope for CVE-2026-114938 when /proc/cpuinfo contains avx512vbmi and the JVM build is on an affected train. |
Detection
| Source | Rule | Gap |
|---|---|---|
| Splunk ESCU | None — verified | No ESCU text names CVE-2026-114938 or UseBASE64Intrinsics. |
| Elastic | Partial — Potential Reverse Shell via Java | Public-IP java -jar shell within 5s, not Base64 decode. |
| Sigma | Partial — Suspicious Java Children Processes | Parent /java shell child only, not the Base64 decoder. |
Hunt hint: Run java -version on application hosts and keep any build that matches an Oracle affected row or that is older than the Temurin build for that train. On Linux, read /proc/cpuinfo and flag avx512vbmi. Set -XX:-UseBASE64Intrinsics and confirm the flag is on the running command line or in JAVA_TOOL_OPTIONS. Talos reports exploitation is unconfirmed, so a JVM crash on a Base64 path is a lead, not proof. After the new build is running, confirm java -version matches the row for that train.
Sources: OpenJDK advisory, Oracle CPU, Adoptium, Talos, The Hacker News.
Detection index: ESCU a9ef36bfc90f (2026-11-16) · elastic detection-rules c678d34edbaa (2026-11-17) · SigmaHQ 698f0912f571 (2026-11-18).
Status Updates
- Apple (CVE-2024-27834): Apple-CVE-2024-27834-2026-11 is KEV due today, 18 Nov. No new build. 17 Nov brief.
- Check Point Gaia (CVE-2026-123039): CheckPoint-Gaia-CVE-2026-123039-2026-11 stays overdue (due 16 Nov). Check Point Research now ties PHP2Shell on the Mobile Access portal to this bug, with webshells,
/tmp/CPconfigdaemon, and a follow-on ESXi wipe. Check Point Research, 13 Nov brief. - Openwave Webtop (CVE-2026-111793): Openwave-Webtop-CVE-2026-111793 is not yet briefed. KEV remains due 24 Nov. The vendor fix remains 1.1.22.0. Advisory, 17 Nov brief.
- UnrealIRCd (CVE-2026-114713): UnrealIRCd-CVE-2026-114713-2026-11 remains overdue (due 16 Nov). The fix remains 6.2.7.1. Forum, 17 Nov brief.
- Barracuda ESG (CVE-2026-116606): Barracuda-ESG-CVE-2026-116606-2026-11 remains overdue (due 13 Nov), with CVE-2026-111560. No new material. Trust Center, 17 Nov brief.
- OpenSSH (CVE-2026-123158): OpenSSH-CVE-2026-123158 remains overdue (due 12 Nov). The fix remains 10.6p2. OpenSSH notes, 17 Nov brief.
- GPUStack (CVE-2026-102895): GPUStack-CVE-2026-102895 remains overdue (due 12 Nov). The fix remains 2.3.0 or a later stable release. Advisory, 17 Nov brief.
- FreeSWITCH (CVE-2026-116779): FreeSWITCH-CVE-2026-116779 remains overdue (due 12 Nov). The fix remains 1.11.3. Advisory, 17 Nov brief.
- IBM Aspera Faspex (CVE-2026-123218): IBM-Aspera-Faspex-CVE-2026-123218 remains overdue (due 12 Nov). The fix remains 5.0.19 PL1. IBM bulletin, 17 Nov brief.
- SonicWall SonicOS (CVE-2026-19868): SonicWall-SonicOS-CVE-2026-19868 remains due 20 Nov. The fix remains 7.3.4-7013 and 8.2.3-8015, already established on 7 Nov. SNWLID-2026-0014, 17 Nov brief.
- Microsoft Outlook (CVE-2026-124194): Microsoft-Outlook-CVE-2026-124194 remains due 24 Nov. The fix remains 16.0.14334.21048 and 16.0.17932.21140. MSRC, 17 Nov brief.
- Chrome (CVE-2026-125350): Chrome-CVE-2026-125350-2026-11 remains due 24 Nov. The fix remains 157.0.8103.50 and 157.0.8103.51. Chrome releases, 17 Nov brief.
- Cisco BroadWorks (CVE-2026-20320): Cisco-BroadWorks-CVE-2026-20320 remains due 24 Nov. The fix remains RI.2026.07. Cisco, 17 Nov brief.
- Retired from watch: CVE-2026-41709 (VMware ESX insufficient logging). KEV was due 11 Nov and the last material update was 29 Oct. No new build or exploitation detail today. 17 Nov brief.
- Watching (no change): ARTEX-Software-Vendors-2026-11; Barracuda-Cloud-ARTEX-Intrusion-2026-11; Binance-TraderTraitor-2026-11; Copeland-XWEB-EVO-2026-11; Cursor-Fireworks-Key-Compromise-2026-11; GitHub-wfx-loot-CI-stealer-2026-11; LNbits-server-shutdown-2026-11; N-able-NCentral-Able2Shell-2026-11; Optimizely-OPTIMJACK-Supply-Chain-2026-11; Refrigeration-Controllers-EU-2026-11; ScreenConnect-CryptoBait-Sessions-2026-11; ScreenConnect-SCKit-RMMplus-2026-11; Windows-SignDrop-LPE-2026-11; Zyxel-GS1900-CVE-2026-107441; eMudhra-CVE-2026-111943 (17 Nov brief).