Rose debug info
---------------

Programmer’s Digest #211

11/11/2026-11/18/2026 Attackers Compromise Microsoft’s Agent Framework PyPI Package; PostgreSQL CVE-2026-6460 and 51 More Flaws Fixed; Critical Java4Shell Flaw And More.

1. Attackers Compromise Microsoft’s Agent Framework PyPI Package to Steal Cloud Credentials

Threat actors compromised Microsoft’s agent-framework package on PyPI, publishing malicious versions 1.26.1 and 1.26.2 33 minutes apart on November 17, 2026. Both have since been quarantined, and it’s unclear how the attacker gained publishing access. The package draws about 190,000 downloads a month.

Each version drops a .pth file into site-packages, so the stealer runs on every Python start, even when the package is never imported. It harvests environment variables, credential files (Azure CLI, .npmrc, pip.conf, .netrc, .git-credentials, Docker, Hugging Face, .env), Azure DevOps OIDC tokens, and managed-identity tokens. It also requests fresh tokens from the platform, so rotating stored secrets alone isn’t enough. Data is compressed, encoded, and sent to a webhook.site endpoint. Version 1.26.2 also collects GitHub Actions OIDC tokens.

Users should isolate affected hosts and runners, pin to safe version 1.26.0, check for exposure between 8:35 and about 9:20 p.m. UTC on November 17, search logs for the webhook.site endpoint, rotate credentials from a clean system, and audit Azure identities and GitHub Actions workflows.

It is the second Microsoft PyPI package compromised this year, after durabletask in May 2026.

2. PostgreSQL CVE-2026-6460 and 51 More Flaws Fixed in November 2026 Updates — Patch Now

PostgreSQL released 18.7, 17.12, 16.16, 15.20 and 14.25 on 12 November 2026, fixing 52 security vulnerabilities. The most serious, CVE-2026-6460 (CVSS 8.8 High), is a type confusion flaw that lets an attacker with permission to create database objects execute arbitrary code as the operating system user running the database. It is not unauthenticated. No exploitation has been reported, CISA lists exploitation as “none”, and the CVE is not in the KEV catalog.

Another 31 fixes also score 8.8, many involving code execution in PL/Perl, PL/Tcl, dblink, logical replication and client tools such as pg_dump and pg_restore. All earlier versions are affected. PostgreSQL 14 is now end of life, so 14.x users should update to 14.25 and plan a major upgrade.

Updating needs only a binary swap, with no dump and reload. C-language extensions must be rebuilt, and some need source changes. After updating, reindex certain GIN, pg_trgm GiST and bpchar B-tree indexes, and take a new full backup if using incremental backups. Until patched, restrict who can log in and create objects.

3. Hackers Compromise 4,800 GitHub Accounts to Steal Cloud Credentials

A campaign dubbed “wfx-loot” targeted tens of thousands of GitHub repositories to steal Actions secrets and cloud credentials. Researchers at Aikido confirmed secrets were stolen from at least 1,835 targets.

Starting around 12:45 UTC on November 10, the attacker used 4,837 compromised accounts, some belonging to Fortune 100 firms, the US General Services Administration, the French government, Nextcloud and WebdriverIO, to probe 61,764 repositories for write access. Pull requests titled “docs: dependency audit notes” were opened, and 92% remain open. About 50 accounts also hold publishing rights on ecosystems such as npm, PyPI, Go, crates and Packagist.

Where access was sufficient, a 1,500-line shell script was injected via a modified or new workflow, or an npm install hook. It harvested GitHub tokens, AWS, Azure and Google Cloud credentials, developer and AI service keys, and other secrets. It could also escalate cloud privileges through OIDC token exchange and create persistent access. Data was exfiltrated over HTTP POST, and traces were deleted within a minute.

The payload also reached a Packagist package and two Go module versions through automated publishing.

Owners should check for the “wfx-docs” branch, the probe pull request and gaps in workflow run numbers, and rotate all exposed secrets and cloud roles immediately.

4. Critical Java4Shell Flaw Allows RCE Attacks On Major Java Applications

“Java4Shell” (CVE-2026-114938) is a critical memory-corruption flaw in OpenJDK’s hardware-accelerated Base64 decoder that can leak memory or allow remote code execution. Calif researchers rated it 9.2 (CVSS 4.0), while Oracle rates it 8.1 High.
It affects OpenJDK 17.0.6 and later, plus distributions built from it, including Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK. Specially crafted Base64 data, as little as 64 “A” characters followed by “=”, can corrupt memory. Only x86-64 processors with AVX-512 VBMI support are affected.

Calif achieved unauthenticated RCE against Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, and authenticated RCE against Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. There is no universal exploit, since attackers need an application-specific way to deliver the data. Researcher Quang Luong found the bug in about an hour using OpenAI’s Codex. A proof-of-concept is public, but weaponized exploits are not.

Oracle patched the flaw on November 17. Temporary mitigations are launching Java with -XX:-UseBASE64Intrinsics or -XX:UseAVX=2, but updating is still advised.

5. CISA Urges Immediate Patching of Java4Shell Flaw That Could Allow Remote Code Execution

CISA has urged organizations to immediately patch a critical Oracle Java flaw, CVE-2026-114938 (CVSS 8.1), dubbed “Java4Shell.” The out-of-bounds write bug affects the Base64 decoder in the x86-64 HotSpot JVM, part of the JDK. Specially crafted Base64 input can crash the JVM and enable unauthenticated remote code execution.

Oracle and OpenJDK have released patches, and no in-the-wild exploitation has been reported so far. Under default settings, attackers without an account can execute code on Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins, and PingFederate. Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, and Spinnaker are exposed to authenticated attackers.

Blackpoint Cyber tested a Spring Boot application using Spring Security. Roughly 28,000 unauthenticated requests with a malformed Base64 value crashed the JVM in about 20 seconds. Testing also showed corruption of nearby Java objects and altered live application data without an immediate crash.

CISA recommends identifying affected Java installations, reviewing inventories for JDKs and runtimes bundled in third-party software, containers, and appliances, and applying patches promptly. If patching isn’t possible, organizations should validate Base64 input, enforce size limits, and restrict unauthenticated access.

6. 16 Severe Node.js Vulnerabilities

The Node.js project released security updates on November 11 for its supported lines, v26.13.1, v24.22.3, and v22.23.5. They fix 16 vulnerabilities, seven rated “high,” all in the native HTTP/2, HTTPS, and TLS server code. Unauthenticated attackers can exploit them on default configurations, crashing server processes or leaking memory, including TLS private keys.

The high-severity flaws include:

  • CVE-2026-123863: crashes default HTTP/2 servers (24.x, 26.x).
  • CVE-2026-123864: exposes other connections’ memory on HTTPS servers.
  • CVE-2026-123865: permanently retains HTTP/2 memory and file descriptors.
  • CVE-2026-123866: sends freed memory over HTTP/2.
  • CVE-2026-123872: bypasses client-certificate rules via TLS 1.2 renegotiation.
  • CVE-2026-123874: corrupts memory when serving files (24.x, 26.x).
  • CVE-2026-126051: crashes TLS servers (24.x, 26.x).

Unless noted, all three lines are affected. Five reports came from Chris Rohlf with Anthropic Research. End-of-life lines such as 20.x and 25.x get no fixes. No workarounds exist, and no exploitation has been confirmed. Servers exposed directly to the internet face the greatest risk, and teams should also review how TLS keys are handled.

7. Critical Red Hat Quay Flaw Lets Attackers Read and Overwrite All Private Container Images in a Registry

Red Hat disclosed two critical flaws in Quay, its container registry. The first, CVE-2026-123710 (CVSS 9.8), lets an attacker read and overwrite private images in every repository. Quay’s key server doesn’t verify that a token was issued for key rotation, so an anonymous token from the /v2/auth endpoint can add an attacker’s key with no expiry. Quay then accepts tokens signed with it for any repository. Disabling anonymous access doesn’t help, since any valid account can exploit it. The planted key survives restarts and password resets, and can delete legitimate keys, breaking pushes and pulls.

The second, CVE-2026-110697 (CVSS 9.9), lets a user who can create a namespace steal other tenants’ robot account tokens. Unescaped SQL LIKE wildcards let an underscore in a namespace name match another tenant’s.

All Quay 3 and 5 versions are affected; fixes exist for eight Quay 3 branches. Red Hat advises blocking the /keys endpoint, auditing logs for null-expiry key events, removing unknown keys, and updating. Quay.io is already fixed.

8 h   digest   programmers'