Back to dashboard

Tech News

Curated security, hosting and development news with vulnerability warnings from fixed trusted sources.

CISA KEVGHSACERT.atHosting

Updated

About these news

Articles are collected periodically from a fixed source list. D4rC Tools stores the headline, source summary and source link only; linked articles are not fetched on page view.

Security Severity: Critical CVE-2026-130001 GHSA-5HRJ-7FC3-CMX9

Mustache for Ruby: RCE using built-in method access

GitHub Advisories

> [!NOTE] > The vulnerability was fully disclosed to the maintainer in private prior to security advisories were enabled for the project. > This advisory presents a limited information for initial release to provide a time window for installing updates. Full information with PoCs would be added later. ## Summary Mustache template engine for Ruby in versions 1.1.2 and earlier allows remote attackers to achieve arbitrary code execution through accessing specific built-in methods in an attacker-supplied template. ## Details Mustache is often suggested as a safe simple template language to avoid SSTI vulnerabilities.[^1] [^2] Mustache for Ruby up to version 1.1.2 did not properly restrict method access which allowed chaining multiple built-in methods to achieve arbitrary code execution. > [!I…

Security Severity: High CVE-2026-63496 GHSA-XVCC-VQJV-PHQH From dashboard

augment-virShell allows Command Injection in `grep()` via Unsanitized `searchPattern`

GitHub Advisories

## Shell Command Injection in grep() via Unsanitized searchPattern ### Summary The grep() function exported by @augment-vir/node inserts caller-controlled search patterns directly into a double-quoted shell command string without sanitization (grep.ts:310). When the constructed command is passed to spawn() with shell: 'bash' (shell.ts:98-99), bash evaluates $() command substitution expressions embedded in the pattern, resulting in arbitrary OS command execution as the Node.js process user. Any downstream application that passes untrusted input to grep()'s pattern or patterns field is vulnerable to unauthenticated local (and potentially remote) code execution. CVSS Base Score: **7.8 (High)**. ### Details **Root cause:** packages/node/src/augments/fs/grep.ts:310 ma…

Security Severity: Medium CVE-2026-61618 GHSA-265X-V3QF-FF6P

snark-verifier accepts non-canonical KZG accumulator limb encodings

GitHub Advisories

### Summary KZG accumulator public-instance limbs were decoded without consistently enforcing canonical limb bounds before reconstructing elliptic-curve coordinates. In the generated EVM verifier, accumulator coordinates were reconstructed from public-instance limbs using shifted additions before point validation. The verifier checked the reconstructed point, but did not independently check that every limb was below the configured limb bound before reconstruction. ### Details PlonkProof::read takes accumulator public-instance scalars selected by accumulator_indices and passes them into AccumulatorEncoding::from_repr. For the EVM loader, LimbsEncoding::from_repr forwards those limbs to EvmLoader::ec_point_from_limbs, where each coordinate was reconstructed with shl and add be…

Security

Kritische Sicherheitslücken in NGINX Plus und NGINX Open Source - Updates verfügbar

CERT.at

18. November 2026 Beschreibung In NGINX Plus und NGINX Open Source existieren mehrere Sicherheitslücken in den Modulen ngx_http_v2_module (HTTP/2), ngx_http_v3_module (HTTP/3) und ngx_mail_proxy_module (Mail-Proxy). Es handelt sich um Use-after-free-Schwachstellen sowie einen Heap-Buffer-Overflow, deren Ausnutzung zum Absturz von Worker-Prozessen und unter bestimmten Voraussetzungen zur Ausführung von beliebigem Code führen kann. F5 bewertet die Schwachstellen nach CVSS v4.0 als kritisch. CVE-Nummer(n): CVE-2026-123007, CVE-2026-121810, CVE-2026-123633, CVE-2026-113425 CVSS Base Score: jeweils 8.1 (CVSS v3.1) bzw. 9.2 (CVSS v4.0) Auswirkungen Durch Ausnutzen der Schwachstellen können Angreifer:innen aus der Ferne NGINX-Worker-Prozesse zum Absturz bringen (Denial-of-Service) oder deren Spe…

Hosting & Network

How Cloudflare WAF helps protect against Java4Shell (CVE-2026-114938)

Cloudflare

Java4Shell is a critical memory-corruption flaw in OpenJDK's Base64 decoder that can lead to remote code execution. Cloudflare has released six WAF managed rules for paid plans that logs matching requests by default. Patch your Java runtimes now.

Security

New EggStreme Malware Variant Goes Silent to Evade Security Tools in Government Attacks

The Hacker News

The suspected Chinese advanced persistent threat (APT) group behind the sophisticated EggStreme malware has rebuilt its toolkit as it continues to target government organizations in the Philippines. "When attackers are exposed, the cheap response is to rotate," Bitdefender said in a technical report shared with The Hacker News. "A file hash changes with every recompile, a domain costs a few

Security

Kritische Sicherheitslücke in Java (Java4Shell) - Updates verfügbar - CVE-2026-114938

CERT.at

18.11 2026 Beschreibung In Java existiert eine kritische Sicherheitslücke, die es nicht authentifizierten Angreifer:innen ermöglicht, Schadcode aus der Ferne auszuführen. Betroffen sind Programme die Java 17.0.6 oder später verwenden, beispielsweise Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, und PingFederate. Mit einem authentifizierten User konnte Remote Code Execution auf Plattformen wie Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, und Spinnaker erzielt werden. Schadcode kann ausschließlich auf x86-64 Intel und AMD Prozessoren welche das AVX-512 VBMI Instruktionsset unterstützen. Die Memory Corruption kann durch 64 Zeichen in Kombination mit einem `` =` ausgelöst werden (respektive 128 Zeichen für ältere OpenJDK Versionen), und im schlimmsten…

Security

New Attack Bypasses TPM Lockout to Crack Windows Hello and BitLocker PINs in Days, Not Years

The Hacker News

On AMD-based PCs and some Intel PCs, the TPM lockout for Windows Hello and BitLocker PINs can be reset by someone who opens the PC's case, researchers at Technische Universität Berlin say. That leaves short PINs open to guessing. In lab tests, the researchers found a four-digit Hello PIN on an AMD laptop and a 6-digit BitLocker PIN on an Intel laptop this way. Both PINs were set by the

Security

AI Pentesting Checklist for Web Apps: 15 Questions to Ask Before Choosing a Vendor

The Hacker News

TL;DR Attackers move first. On average, exploitation now starts before a patch exists (Mandiant M-Trends 2026). In 1H 2026, 23% of vulnerabilities VulnCheck added to its exploited list were hit on or before disclosure day. AI pentesting vendors aren't interchangeable. Most look convincing in a demo. The gaps show up in your logged-in flows, your coverage, and your production safety. Make

Security

Quality Isn’t The Main Worry About AI Pentesting — Data Privacy and Production Safety Are

The Hacker News

AI is speeding up how software is built, which means more code, more changes, and more chances for vulnerabilities to reach production. It's speeding up how attackers find and exploit them too, with time-to-exploit now down to a single day. Security testing has to keep up with both. AI pentesting has emerged as a way to run in-depth tests whenever teams need them, instead of waiting for the

Security

Hackers Exploiting Critical Puppet RCE Flaw Affecting Enterprise Management Servers

The Hacker News

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Tuesday added a critical security flaw impacting Perforce Puppet, an enterprise infrastructure-as-code (IaC) and configuration management platform, to its Known Exploited Vulnerabilities (KEV) catalog, citing reports of active exploitation. The vulnerability, tracked as CVE-2026-115731 (CVSS score: 9.4), is a case of

Security

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

The Hacker News

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has urged organizations to immediately patch a newly disclosed critical security flaw impacting Oracle Java. The flaw, tracked as CVE-2026-114938 (CVSS score: 8.1), refers to a case of out-of-bounds write that can lead to denial-of-service (DoS) or remote code execution under certain conditions. "This critical memory-corruption

Security

Attackers Compromise Microsoft's Agent Framework PyPI Package to Steal Cloud Credentials

The Hacker News

Threat actors have compromised Microsoft's agent-framework package to push a credential stealer, according to reports from Aikido, Endor Labs, OX Security, SafeDep, Socket, StepSecurity, and Google-owned Wiz. The malicious versions, 1.26.1 and 1.26.2, were published 33 minutes apart on November 17, 2026, and are designed to run a credential stealer on every Python start. As of writing, both the

Security

Russian COLD RELIC Hackers Use Stolen Google Workspace Data to Breach Second U.S. Organization

The Hacker News

The Russia-linked cyber espionage group known as Cold Relic (formerly COLDRIVER and UNC4057) has been observed weaponizing a single cloud compromise into a launchpad for a series of linked intrusions resulting in third-party compromise. Google's Mandiant and Threat Intelligence Group (GTIG) said it investigated a 2026 compromise at a U.S.-based organization in which the adversary leveraged

Security

Java4Shell (CVE-2026-114938) Enables Pre-Auth RCE in Jira, Jenkins, Keycloak on Java 17+ AVX-512 VBMI Servers

The Hacker News

A Java flaw called Java4Shell can let attackers without an account run their own code on Jira, Jenkins, Keycloak, and three other widely used applications, says Calif, the security research firm that disclosed it this week. The flaw is present in Java 17.0.6 and later, and the vulnerable code runs only on x86-64 Intel and AMD chips that support the AVX-512 VBMI feature. Tracked as

Security Severity: High CVE-2026-119793 GHSA-X2VM-CF3P-M2W8

libp2p: gossipsub creates a permanent topics-map entry per distinct subscription with no cap in the default config

GitHub Advisories

### Summary A single gossipsub peer can grow a node's topics map without bound by flooding subscription RPCs, because the default configuration has no global, per-peer, or topic-length cap and peer scoring does not penalise subscription volume. The peer is never greylisted, so the growth continues toward OOM. ### Details handleReceivedSubscription (packages/gossipsub/src/gossipsub.ts:1028, line 1036) runs this.topics.set(topic, new Set()) for every distinct topic string: ``ts private handleReceivedSubscription (from, topic, subscribe) { let topicSet = this.topics.get(topic) if (subscribe) { if (topicSet == null) { topicSet = new Set() this.topics.set(topic, topicSet) // no global cap, no per-peer cap } topicSet.add(from.toString()) } } `` The only topical gate (`gossipsub.ts:981…

Security Severity: High CVE-2026-110789 GHSA-RVFR-CQWQ-RC4J

libp2p: ASN.1 DER decoder drives an unbounded synchronous loop on attacker-controlled length fields, stalling the Node event loop pre-auth

GitHub Advisories

### Summary A remote peer can stall a js-libp2p node's entire event loop for ~4–5 seconds per connection (and transiently allocate ~2 GB) by sending a ~15-byte crafted publicKey inside an Identify message. The malformed key reaches the DER decoder before any peer-id/signature check, so the attack is pre-auth and repeatable indefinitely by reconnecting. ### Details packages/crypto/src/keys/rsa/der.ts readLength() parses DER long-form lengths with no comparison to buf.byteLength, and readInteger() then loops over the attacker-claimed length: ```ts function readInteger (buf, context) { const length = readLength(buf, context) // attacker-controlled, claims up to 2^64 const end = context.offset + length for (let i = context.offset; i < end; i++) // runs far past buf.byteLength vals.p…

Security Severity: High CVE-2026-110782 GHSA-R7HW-JX6R-756G

SAML2: Incomplete fix of CVE-2026-49283: unsigned embedded Response bypasses HTTP-Artifact signature verification (no embedded-Issuer binding)

GitHub Advisories

## Summary CVE-2026-49283 / GHSA-6929-8p9f-26jx ("HTTP-Artifact TLS validator confusion allows cross-IdP authentication bypass") was fixed so that HTTPArtifact::receive() verifies the embedded SAML Response using the IdP metadata signing keys. The current implementation (master 31c72c1d, released **v6.2.3**) reaches that verification **only when the embedded Response is signed**: ``php // src/Binding/HTTPArtifact.php (receive()) if (!$samlResponse->isSigned()) { return $samlResponse; // ← unsigned embedded Response returned UNVERIFIED } return $this->verifyMessageSignature($samlResponse, $idpMetadata); // only runs when signed `` An attacker who controls one trusted-federation IdP therefore returns a **validly-signed outer ArtifactResponse** (signed with their own real key, whic…

Security Severity: Medium CVE-2026-69241 GHSA-8VM9-F75M-5H2M

Filament Curator: Stored XSS via unsanitized SVG upload served inline

GitHub Advisories

## Summary SVG files uploaded through the Curator media panel are stored and served inline without any sanitization. An authenticated user with permission to upload media can upload an SVG containing embedded JavaScript. When another panel user opens that file via the **View** action (which opens the media as a top-level browser document), the embedded script executes in the origin of the Filament application. image/svg+xml is included in the default accepted MIME types, so a default installation is affected unless SVG uploads have been explicitly disabled. ## Impact Because the SVG is served as a **top-level document** (not embedded in an `` tag), any ``, event-handler attribute (e.g. onload), or javascript: URI inside it runs with full script privileges in the application's origin…

Security Severity: Medium CVE-2026-63389 GHSA-828W-6QGX-3RCF

Filament Curator: Cross-tenant media metadata disclosure via Curator picker search

GitHub Advisories

Summary In multitenant Filament panels, an authenticated user could retrieve media metadata belonging to other tenants by typing in the Curator media-picker search box. The search query omitted the tenant ownership scope that the normal file listing applies. Details CuratorPanel::updatedSearch() built its Eloquent query independently of getFiles() and did not apply the filament()->hasTenancy() && $isTenantAware tenant-ownership where clause. As a result, the search matched media across all tenants. A secondary flaw compounded it: the orWhere('title'…) chain was not wrapped in a nested group, so the OR conditions also broke out of the isLimitedToDirectory constraint. The issue was introduced in v3.2.4, when multitenancy support was added to the media picker. Impact - Who: any authenticated…

Security Severity: High CVE-2026-62336 GHSA-XHV5-8FPQ-G7HF

qbee-agent: Local Privilege Escalation and Arbitrary File Tampering via Symlink Following in createFile helper

GitHub Advisories

This is a Local Privilege Escalation (LPE) vulnerability stemming from improper symlink handling (CWE-59: Link Following) and improper ownership management (CWE-282) inside the qbee-agent file manager logic. ### Impact Any managed device running qbee-agent up to the affected versions. The impact manifests in three distinct vectors: 1. **Primary Vector (Full Privilege Escalation to Root - Default Configuration)**: If an unprivileged user's account is managed by the SSH Keys bundle, they can replace or remove their own ~/.ssh directory and create a symlink pointing to /root/.ssh. On the next configuration apply, qbee-agent follows the symlink and writes the user's server-provisioned public key directly into /root/.ssh/authorized_keys. Since the symlink resides inside the user's own ho…

Security Severity: Medium CVE-2026-63672 GHSA-PR4X-6FJ4-GM4H

EGroupware: User-Controlled Identity Provider Selection in SAML Authentication

GitHub Advisories

### Summary The login() function at line 130 passes the raw user-supplied value $_REQUEST['idp'] directly to SimpleSAMLphp's requireAuth() with only a regex check that the string starts with 'https://'. No validation is performed against a list of configured, trusted IdP entity IDs. An unauthenticated attacker can supply any HTTPS URL pointing to an IdP they control. ### PoC ``php //api/src/Auth/Saml.php function login() { // login (redirects to IdP) $as = new SimpleSAML\Auth\Simple(self::$auth_source); $as->requireAuth(preg_match('|^https://|', $_REQUEST['idp']) ? ['saml:idp' => $_REQUEST['idp']] : []); `` ### Impact An attacker can redirect authentication to a malicious IdP to capture credentials via phishing, or, if the SimpleSAMLphp configuration does not strictly validate IdP m…

Security Severity: High CVE-2026-14265 GHSA-C5Q4-97JW-JGGH

AWS-advanced-jdbc-wrapper: Java Deserialization RCE via Cache Poisoning

GitHub Advisories

### Impact The AWS Advanced JDBC Wrapper is an open-source JDBC driver wrapper that extends a JDBC driver to enable Amazon Aurora and AWS Cloud features such as failover handling and caching. We identified CVE-2026-14265, an issue in the RemoteQueryCachePlugin of the AWS Advanced JDBC Wrapper. When this plugin is enabled, query results read from the shared Redis/Valkey cache are deserialized without class filtering. An actor with write access to the shared cache infrastructure could insert a crafted serialized Java object that, when read by an application, results in execution of arbitrary code on the application server. ### Workarounds The RemoteQueryCachePlugin is not enabled by default. Customers who cannot immediately upgrade can mitigate this issue by disabling the RemoteQueryCachePl…

Hosting & Network

Quad9’s withdrawal from France: A canary in the coal mine

Cloudflare

Quad9's forced withdrawal from France highlights the dangers of mandating DNS-level blocking. We explore why forcing public resolvers to act as content filters is technically flawed and threatens the open Internet.

Security Severity: Medium CVE-2026-63634 GHSA-V858-XH7W-8JR5

pympp allows excessive sponsored transaction fees through padded calldata

GitHub Advisories

### Details When the server acts as the fee_payer, pympp 0.8.0 validates calldata using eth_abi decoding, which is lenient about trailing bytes. The FeePayerPolicy caps gas_limit (≤ 2 M) and max_fee_per_gas (≤ 100 Gwei) but does **not** check calldata length. Tempo uses legacy calldata gas pricing: **16 gas per non-zero byte**. Appending N bytes of 0x01 padding inflates actual gas used by N × 16 while keeping gas_limit and max_fee_per_gas within policy caps. The server cosigns and broadcasts the padded transaction, draining its fee-payer wallet. **Vulnerable code path:** FeePayerPolicy in fee_payer_policy.py (pympp 0.8.0) enforces maxGas = 2_000_000 and maxFeePerGas = 100 Gwei but has no calldata.length bound. The policy check passes because the inflated gas…

Security Severity: Critical CVE-2026-53998 GHSA-GFV3-M769-5XM3

Phoenix: Format String Injection in applyChatTemplate

GitHub Advisories

- Summary A format string injection vulnerability in the applyChatTemplate GraphQL endpoint allows an attacker to read server-side environment variables, cryptographic secrets, and internal module attributes directly from the API response. On default Phoenix installations where authentication is disabled the endpoint is reachable with no credentials. On auth-enabled deployments, any account regardless of privilege level is sufficient to exploit it. - Impact Server filesystem paths, loaded Python module names, and internal configuration constants are fully disclosed, an attacker with network access can read the full server os.environ including the admin credentials hardcoded in phoenix.auth. Successful exploitation allows an attacker to extract PHOENIX_SECRET, the master key used to si…

Security

Researchers Claim Two RCE Exploits That Bypass Telegram’s New Android Defenses

The Hacker News

A malicious widget can bypass the security filter that Telegram added to its Android app last week and run code outside it, according to NebuSec, a security company. Widgets are small interactive blocks that bots send inside chat messages, and their JavaScript runs on the user's phone. The researchers ran their demonstration on a Telegram test server, because only approved bots can send

Security Severity: Medium CVE-2026-119351 GHSA-VC7V-QV4W-WRV8

Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata

GitHub Advisories

With Cache Components enabled, an outer 'use cache' function can be keyed incorrectly even when its inner 'use cache' call generates a fresh entry. If the inner function reads a root param (via next/root-params) and returns a value that still contains pending promises — for example an object with data that is ready immediately alongside slower data — React Flight delivers the ready portion to the outer function before the inner entry has finished publishing its root param dependencies. The outer function can then finish, and its cache entry is persisted under a key that omits that root param. The entry is written once and reused for all root param values, so a response for one root param value can serve content produced for a different value. Entries written this way can also ignore…

Security

Oracle to Patch 11 Java Flaws Today as Critical OpenJDK RCE (CVE-2026-114938) Report Emerges

The Hacker News

Oracle is preparing to release security patches for 11 vulnerabilities in Java SE on Tuesday, November 17, 2026, all of which may be exploited remotely without authentication, as separate reports warn of a potentially critical remote code execution (RCE) flaw affecting OpenJDK. The 11 vulnerabilities carry a maximum CVSS 3.1 severity score of 8.1, according to Oracle's advance security notice.

Security

Trigram Campaign Impersonates About 50 AI and Blockchain Brands to Target Devs with Infostealers

The Hacker News

Artificial intelligence (AI), blockchain, and logistics sectors across Europe and the U.S. have emerged as the target of a large-scale, industrialized campaign dubbed Trigram. "Trigram is a large-scale campaign that impersonates about 50 brands in the blockchain and AI sectors, to trick developers into executing an infostealer themselves," Stormshield said in a deep-dive technical report

Security

Hackers Found a Way Around GitHub SHA Pinning. This Webinar Explains How to Close the Gap

The Hacker News

Pinning GitHub Actions to an exact version of their code, known as SHA pinning, has become the go-to defense against software supply chain attacks. Attackers have already found a way around it. In March 2026, the hackers who hijacked Trivy, a widely used open-source security scanner, planted malicious code that looked like it came from GitHub's official checkout tool. They even labeled it a

Security

Researchers Detail iPhone Flaw That Let Apps Record Audio Despite Denied Microphone Permission

The Hacker News

A now-patched flaw in Apple's audio service let apps on iPhones and iPads record audio even after the user tapped "Don't Allow" on the microphone prompt. The first security updates with the fix came out on August 17. Neither Apple nor the two researchers who found the flaw report that it was used in attacks. Nik Tsytsarkin of Meta Red Team X published the technical details last week. Mustafa

Security

New GitDoor and GraphDoor Backdoors Turn GitHub and SharePoint Into Covert C2 Channels

The Hacker News

Government sectors in Asia and Africa have been targeted by an active cyber intrusion campaign that delivers to previously undocumented backdoors that leverage legitimate services like Microsoft SharePoint and GitHub for command‑and‑control (C2). The activity has been codenamed Operation ShadowCloud by Kaspersky. The Russian cybersecurity company said it identified the campaign in early 2026.

Security

Apple Tightens macOS App Permissions to Limit Data Access Amid AI Agent Security Risks

The Hacker News

Apple on Monday introduced new controls that allow Mac users to give more granular access to data they give to apps, including those that use artificial intelligence (AI) agents. The changes, currently previewed in macOS 27.3 beta 2, relate to increased transparency and more options for two of its APIs: Device Control and Data Access, and Full Disk Access. "Before granting an app such

Security

Hijacked Optimizely Scripts Served Card Skimmer and iOS Exploit Kits to CNN, BBC and Zoom Visitors

The Hacker News

An attacker exploited a flaw in Optimizely Web Experimentation to plant malicious code in some of the scripts that customers' websites load from the service, Optimizely said early today. Visitors to sites run by at least 178 organizations, including CNN, the BBC and Zoom, received the code yesterday, according to Report URI, a firm that monitors the scripts websites run. The code was built to

Security

ConnectWise Warns ScreenConnect Attacks Continue as SCKit Targets Unpatched Systems

The Hacker News

ConnectWise on Monday said it completed its investigation into unauthorized access targeting partner ScreenConnect environments, and recommended customers to ensure that the technician client is running version 26.6.5 or later. The company said additional activity targeting on-premises environments continues to be reported where the identified third-party extensions remain enabled, and

Security

N-able Patches 17 N-central Flaws as Attackers Exploit Earlier Bugs to Deploy Crypto Miners

The Hacker News

N-able has released a new security update to address additional critical security flaws impacting N-central. Describing N-central 2026.4 Hotfix 3 as a critical security update, the company said it includes a number of security patches and fixes that enhance the security of the Remote Monitoring and Management (RMM) and Unified Endpoint Management (UEM) platform. "HF3 builds on the

Security Known exploited CVE-2026-115731

Perforce Puppet Enterprise: Perforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability

CISA KEV

Perforce Puppet Enterprise contains a deserialization of untrusted data vulnerability in Puppet’s report-processing code that allows a client with any CA-signed agent certificate to execute arbitrary code on the Puppet Server as the service user by submitting a report containing a crafted rich-data type through a PUT request. If the certificate authority automatically signs requests without strong verification, an unauthenticated network attacker can obtain a valid certificate and exploit the vulnerability.

Required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CISA due date: 2026-12-01

Security Severity: Medium CVE-2026-129237 GHSA-VX32-XF7G-9GHR

qbee-agent: Docker Compose build context Zip Slip writes outside context directory

GitHub Advisories

## Summary qbee-agent contains a Zip Slip vulnerability in app/utils/tar.go. The tar extractor checks whether an entry remains inside the destination directory with: ``go strings.HasPrefix(targetPath, destdirClean) `` This does not enforce a path separator boundary. If the destination directory is /tmp/.../context, a tar entry such as ../context-outside/payload.txt cleans to /tmp/.../context-outside/payload.txt and still passes the prefix check. qbee-agent then creates the outside directory and writes the payload outside the intended extraction root. The issue is reachable through the Docker Compose build context path when UseContext is enabled. ## Details Code references below were verified against qbee-io/qbee-agent commit: - 1d8bdbb7422adb4ca563d3114cbe2817d6ba3581 Af…

Security Severity: High CVE-2026-91115 GHSA-C94F-87XG-65WF

Silverstripe Framework: RCE via i18nTextCollectorTask writer parameter

GitHub Advisories

### Impact The writer option of the i18nTextCollectorTask dev task was passed to the injector without validation. A crafted dev task URL could create arbitrary objects with attacker-controlled constructor arguments and run code on the server. Because the dev task did not ask for confirmation, an administrator could be tricked into running it by following a link. On a site in dev mode, no login was needed. CMS 5 is not affected. ### Reported by Jack Wallace

Security Severity: Medium CVE-2026-91113 GHSA-4QV2-G5VP-WJJW

Silverstripe Framework: User-controlled ClassName allows unauthorized record type change

GitHub Advisories

### Impact A user who can edit a record through a GridField detail form could change the record to an unrelated class, without the permission checks for that class. ### Reported by Lachlan Davidson, Carapace

Security Severity: Medium CVE-2026-91112 GHSA-RG72-5958-C65M

Silverstripe Framework: CMS_ACCESS_SecurityAdmin privilege escalation

GitHub Advisories

### Impact A user with access to the Security section (CMS_ACCESS_SecurityAdmin) but without the ADMIN permission could edit a group that grants ADMIN through a role or a parent group, and use it to escalate their own privileges. ### Reported by Lachlan Davidson, Carapace

Security Severity: Medium CVE-2026-88989 GHSA-3QH3-54QG-GPQ3

Silverstripe Framework: Auth bypass GridFieldDetailForm

GitHub Advisories

### Impact A CMS user who can edit records through a GridField detail form could create new records without the permission to create them, by sending a save request directly. ### Reported by HDWSec - https://hdwsec.fr

Security Severity: Medium CVE-2026-88988 GHSA-XWG4-8HQH-79JQ

Silverstripe Framework: XSS via SVG data URI

GitHub Advisories

### Impact The HTML sanitiser did not remove SVG data URIs. A CMS author could store content that runs JavaScript in the browser of another user who views it. ### Reported by HDWSec - https://hdwsec.fr

Security Severity: Medium CVE-2026-88987 GHSA-QQRG-8JPM-8MPH

Silverstripe Framework: XSS via XHTML data URI

GitHub Advisories

### Impact The HTML sanitiser did not remove XHTML and XML data URIs. A CMS author could store content that runs JavaScript in the browser of another user who views it. ### Reported by Jack Wallace from Bastion Security

Security Severity: Medium CVE-2026-129239 GHSA-7H45-Q5JX-7R87

Directus: Share update allows reassigning user_created and role

GitHub Advisories

### Summary A non-admin user who can update their own shares can reassign a share's creator (user_created), role, item, and collection fields after the share is created. The update is authorized against the row as it existed before the change, and the resulting row is never revalidated, so these fields can be set to values the user would not be permitted to assign when creating a share. By reassigning both user_created and role to an administrator the share's effective permissions get elevated. This is a server-side authorization gap in the share update path. It does not by itself produce an administrator token. It re-opens a previously patched privilege-escalation surface on the effective permissions of a share. ### Prerequisites - An authenticated non-admin account that hold…

Security Severity: Medium CVE-2026-129301 GHSA-8CGQ-X343-P74C

mail-parser: One hostile attachment aborts `write_attachments()` and silently drops the rest of the batch

GitHub Advisories

### Impact write_attachments() called _safe_attachment_filename() and write_sample() inside its loop with no guard, so a single crafted attachment raised out of the whole save. Every attachment **after** the malicious one was silently never written, with no error surfaced to a caller that catches only MailParserError. That is an evasion primitive as much as an availability bug: a sender puts one poisoned part first and the real payload second, and the payload never reaches the extraction directory that a downstream scanner or sandbox reads — while it still reaches the recipient's mail client intact. The tool's output diverges from the bytes actually in the message, which is the same failure mode as the filename-sanitizing bypass in [GHSA-fr3h-cpq2-9496](https://github.com/SpamScop…

Security Severity: Medium CVE-2026-129300 GHSA-XHRQ-2MQV-Q8WX

mail-parser: Uncaught `OverflowError` / `OSError` on an out-of-range `Received` date

GitHub Advisories

### Impact A Received header whose trailing date carries an out-of-range year, or a timezone offset large enough to push the timestamp past the int64 epoch range, raises an exception that is **outside the MailParser* hierarchy**. A caller that catches only mail-parser exceptions does not catch it, and the parse of the entire message is aborted — the same class of issue as [GHSA-24mq-4vc6-2prf](https://github.com/SpamScope/mail-parser/security/advisories/GHSA-24mq-4vc6-2prf), which this survives (it is not a duplicate; 24mq is fixed in 4.6.2 and this reproduces on 4.6.2). All entry points are affected: parse_from_string(), parse_from_bytes(), parse_from_file(), parse_from_file_obj() and the mail-parser CLI. The header is fully attacker-controlled and a single line is enough,…

Security Severity: Medium CVE-2026-129235 GHSA-GJ7R-P794-HHQ5

Kubeshark: MCP `download_file` writes fetched bytes to an unvalidated destination path

GitHub Advisories

**Ecosystem / package:** Go — github.com/kubeshark/kubeshark (the kubeshark CLI, kubeshark mcp subcommand) **Affected component:** cmd/mcpRunner.go, MCP tool download_file **Affected versions:** >= v53.1.0, < v53.4.0 (the flaw shipped with the tool's first release; v53.3.0 was the last affected release) **Patched version:** v53.4.0 **Credit:** novice-22 (Urim), via private coordinated disclosure. ## Summary The download_file MCP tool fetches a caller-supplied path from the Kubeshark Hub API and writes the response body to a caller-supplied dest on the local filesystem with no validation of dest. An attacker who can influence the MCP tool arguments — e.g. via indirect prompt injection against an AI agent driving kubeshark mcp — can write attacker-controlled bytes…

Security Severity: High CVE-2026-129236 GHSA-8VF2-HXG5-CRQH

Kubeshark: MCP `start_kubeshark` argument injection via `pod_regex` → image redirect → cluster takeover

GitHub Advisories

**Ecosystem / package:** Go — github.com/kubeshark/kubeshark (the kubeshark CLI, kubeshark mcp subcommand) **Affected component:** cmd/mcpRunner.go, MCP tool start_kubeshark **Affected versions:** >= v53.1.0, < v53.4.0 (the flaw shipped with the MCP command's first release; v53.3.0 was the last affected release) **Patched version:** v53.4.0 **Credit:** novice-22 (Urim), via private coordinated disclosure. ## Summary The start_kubeshark MCP tool builds a kubeshark tap command by appending the caller-supplied pod_regex as a bare positional argument, with no -- end-of-options separator. Because tap is a cobra command, a pod_regex that begins with -/--set= is parsed as a **flag**, not as the pod regex. An attacker who can influence the tool arguments (e.g. indi…

Security Severity: Medium CVE-2026-129299 GHSA-24MQ-4VC6-2PRF

mail-parser: Uncaught exceptions and silent header loss in mail-parser on attacker-controlled input

GitHub Advisories

### Impact Two effects, sharing the root cause of Advisory 1 — header names chosen by the sender were resolved through Python attribute lookup and rewritten before lookup. **Uncaught exceptions.** A crafted message raises an exception that is *outside* the MailParser* hierarchy, so a caller catching only mail-parser exceptions does not catch it and the worker dies. *Header named after a method* (CWE-248, reported by @iam-niranjan). Python resolves real class attributes before __getattr__, so a header named after a method put a bound method object into the parsed mail dict. A 12-byte email is sufficient. Nine colliding names were confirmed: Parse, Message, Write_Attachments, From_File, From_File_Obj, From_File_Msg, From_String, From_Bytes, Get_Server_Ipaddress. Also r…

Security Severity: High CVE-2026-129297 GHSA-72PX-J8GH-P79X

mail-parser: Sender IP address spoofing in get_server_ipaddress()

GitHub Advisories

### Patches Fixed in **4.6.2**. Upgrade with pip install --upgrade mail-parser. Candidate addresses are now selected by position, not by appearance — a bracketed address the sender wrote is byte-identical to one the MTA wrote, so no amount of pattern matching can tell them apart: - the first token of the from clause is the HELO name, whatever its shape, and is never a candidate; - an explicit HELO marker inside a comment group is sender text and is excluded; - a candidate must sit inside a ( / [ group; - IPv4 and IPv6 matches are merged positionally, never family-first; - the walk stops at the first trusted hop naming no address, rather than continuing into sender-written headers. The IPv6 pattern was corrected to skip the IPv6: tag and to prefer the longest valid form. **Behavi…

Security Severity: High CVE-2026-129295 GHSA-R7W7-VPQ8-C5VV

mail-parser is vulnerable to polynomial ReDoS in email header parsing

GitHub Advisories

### Summary Two regular expressions used while parsing email headers backtrack polynomially on attacker-controlled input. Parsing a single small, well-formed email can consume minutes to hours of CPU, denying service to any process that parses untrusted mail. Both are reachable from an ordinary parse_from_string(), parse_from_bytes() or parse_from_file() call — no special API, option, or malformed structure is required by the victim. ### Details **1. Address-header fallback regex (src/mailparser/utils.py)** get_addresses() falls back to _ADDR_FALLBACK_RE whenever email.utils.getaddresses(strict=True) yields no usable address. The alternative ([^ overlaps a lazy quantifier with an adjacent \s* — a space matches both. Driven by finditer, which retries at every offset and…

Security Severity: Medium CVE-2026-129296 GHSA-FR3H-CPQ2-9496

mail-parser: Path Traversal vulnerability in attachment extraction

GitHub Advisories

A path traversal vulnerability was identified in mail-parser when extracting email attachments using the write_attachments() and write_sample() APIs. A specially crafted email containing malicious attachment filenames (for example, using directory traversal sequences such as "../" or absolute filesystem paths) could cause files to be written outside the intended output directory. Depending on how the library was used and the permissions of the executing process, this could result in arbitrary file overwrite. The vulnerability affects mail-parser versions 3.8.0 through 4.5.0. The issue has been addressed by introducing comprehensive filename sanitization and path validation before any file is written to disk. The fix includes: - Sanitization of attachment filenames before writing. - Valida…

Security Severity: High CVE-2026-86046 GHSA-259W-WMQG-FP76

termux-sync: Arbitrary file write during restore via attacker-controlled manifest source path

GitHub Advisories

termux-sync restore trusts fields inside an untrusted backup manifest and uses them as the extraction destination without validation. During restore, each archive entry is handled as: src_dir = Path(info.get("source", ...)).parent extract_archive(archive, src_dir, ...) extract_archive opens the archive and runs tarfile.extract for every member with no path jail and no filter: with tarfile.open(archive_path, "r:*") as tf: for member in tf.getmembers(): tf.extract(member, dest_path, set_attrs=True) There is no check that manifest "source" stays under an expected restore root, that tar members stay inside dest_path, or that backup_name used in temporary paths cannot contain ".." or separators. Impact: A victim who restores a malicious backup (local, shared, or from a compromised GitHub/Googl…

Security Severity: High CVE-2026-68934 GHSA-JQ3Q-62JC-FQQ9

code-review-mcp-server: Command injection via unsanitized folderPath/baseBranch parameters

GitHub Advisories

### Impact code-review-mcp-server exposes MCP tools (getLocalGitDiff, codeReview, createPR, getPRTemplate) that accept folderPath and baseBranch string parameters. These caller-controlled values were interpolated directly into shell command strings executed via child_process.execSync(), which runs commands through /bin/sh. A crafted value such as baseBranch = "main; #" (or a $(...) command substitution, or a folderPath that breaks out of the surrounding quotes) results in **arbitrary command execution** on the host running the MCP server. ### Patches Fixed in **1.5.3**. Every execSync() call was replaced with execFileSync() using argument arrays, so inputs are passed directly to git / gh without going through a shell, eliminating the injection at its root.…

Security Severity: High CVE-2026-63182 GHSA-W553-PWX6-3MG9

lightsaml allows Signature wrapping bypass

GitHub Advisories

### Summary LightSaml 5.0.0 (latest release; also confirmed on 4.6.1) validates an inbound samlp:Response by collecting its direct-child saml:Assertion elements and validating each one's ds:Signature via robrichards/xmlseclibs. The two layers disagree on which element a signature actually covers: LightSaml reads claims from the assertion node it collected, while xmlseclibs resolves the signed Reference URI="#id" with a document-wide //*[@Id] XPath that returns the first ID-bearing element anywhere in the document. An attacker who has captured one genuine signed assertion can exploit this to surface attacker-authored, unsigned claims. ### Details Response::deserialize collects assertions with manyElementsFromXml, whose relative XPath saml:Assertion matches only direct child…

Security Severity: Medium CVE-2026-119790 GHSA-MFR8-8QWW-V76H

Next.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache()

GitHub Advisories

Next.js applications with 'use cache' can disclose cached data across root params when the same 'use cache' function is called both directly during rendering and through unstable_cache(), and that function reads a root param. Root params are route parameters of the root layout, and applications commonly use them to scope data, for example per locale. During a cold process start, a cross-request deduplication race allowed an unstable_cache() call to join the in-flight fill of a concurrent direct call and receive its result, bypassing the root param check that would normally reject it. unstable_cache() then stored that result under a cache key without root params, so subsequent requests for other root param values received the same entry until it is revalidated or evicted. Cached…

Security Severity: High CVE-2026-128134 GHSA-7MXV-7H3Q-9324

NLTK dot2img runs Graphviz 'dot' without the trusted-exec chokepoint, enabling local code execution via a writable PATH element

GitHub Advisories

## Summary nltk.parse.dependencygraph.dot2img invokes the Graphviz dot executable without the trusted-execution guarantees that NLTK applies to its other native-tool wrappers. The function resolves dot by bare name and then runs the resolved absolute path with a raw subprocess.run, omitting the ownership/writability check and the loader-environment scrub that nltk.pathsec.spawn_trusted provides. On a POSIX host, a local, unprivileged actor who can write to any group/world-writable directory that appears on the victim's PATH can plant a trojan dot; when the victim later renders a DependencyGraph (for example in a Jupyter notebook, which auto-invokes _repr_svg_) or calls dot2img directly, the planted binary executes as the victim. The advisory GHSA-6hwm-xvph-95vm (CVE-20…

Security Severity: Low CVE-2026-128076 GHSA-HF59-9XWC-2G4P

Nuxt: Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)

GitHub Advisories

### Summary The fix for CVE-2026-46342 (GHSA-g8wj-3cr3-6w7v) binds each /__nuxt_island/_.json path to its props by hashing the (name, props, context, source) tuple. That hash was computed over ohash's serialization, which does not escape quotes inside strings or delimiters inside keys, so two different prop objects can produce the same hash. A request with crafted props can therefore pass validation for another island's path and render different content at that path. ### Impact For example, these two prop objects serialize identically and share one island path: ``js { html: '', note: '' } { html: '\',note:\'' } `` This reopens the scenarios described in GHSA-g8wj-3cr3-6w7v: - **nuxt generate / prerendering.** Nuxt caches prerendered island responses by path. If the crawler reach…

Security Severity: Medium CVE-2026-128075 GHSA-96X6-FVHX-49HG

Nuxt exposes the message and data of unhandled errors thrown during server rendering

GitHub Advisories

### Summary When a page, plugin or route middleware throws an error that is not an HTTP error, Nuxt wraps it with createError before rendering the error page. The wrapped error was treated as one the app raised deliberately, so in production its message and data were sent to the client in the error page payload (__NUXT_DATA__) and in JSON error responses. For a failed $fetch, that is the URL that was requested (including its query string) and the body of the upstream error response. ### Impact An application is affected if server-rendered code lets an error with sensitive details reach the error page, for example: ``vue const route = useRoute() // the upstream error body, and the token in the URL, reach the client if this request fails await $fetch(http://users.internal/users/…

Security Severity: Medium CVE-2026-128074 GHSA-R9JC-W898-3FV6

Nuxt payload URL generation has quadratic cost for repeated slashes in the request path

GitHub Advisories

### Summary Nuxt strips trailing slashes from the request path with a regular expression whose cost grows quadratically with the length of a run of consecutive slashes. A single unauthenticated request with a long run of slashes can occupy the server's event loop for a noticeable time, delaying every other request handled by the same process. ### Impact When a page is rendered with payload extraction (any route covered by an isr, swr or cache route rule), Nuxt builds the _payload.json URL from the raw request path. A path such as /blog/a followed by 16,000 slashes and x, which fits within Node's default header size limit, takes roughly 0.1 to 0.4 seconds of synchronous CPU time per request, depending on hardware. Concurrent requests to the same process wait for it to finish, s…

Security Severity: Low CVE-2026-128072 GHSA-X2WV-5868-P7V2

@nuxt/webpack-builder and @nuxt/rspack-builder dev server serves built source to DNS rebinding pages

GitHub Advisories

### Summary When using the webpack or rspack builder, the dev server serves built client chunks to any request whose Host header matches its Origin/Referer, or that carries Sec-Fetch-Site: same-origin. After a DNS rebinding attack both headers name the attacker's hostname, so a malicious page opened while nuxt dev is running can read /_nuxt/*.js and exfiltrate the app's source. This bypasses the same-origin check added for [GHSA-4gf7-ff8x-hq99](https://github.com/nuxt/nuxt/security/advisories/GHSA-4gf7-ff8x-hq99), [GHSA-6m52-m754-pw2g](https://github.com/nuxt/nuxt/security/advisories/GHSA-6m52-m754-pw2g) and [GHSA-x6qj-4h56-5rj5](https://github.com/nuxt/nuxt/security/advisories/GHSA-x6qj-4h56-5rj5). ### Impact A developer runs nuxt dev with builder: 'webpack' or `builder:…

Security Severity: Medium CVE-2026-128071 GHSA-F3X9-2CHM-73C8

Nuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catch-all page routes

GitHub Advisories

### Summary Nuxt matches route rules against the request path with encoded slashes (%2F) left encoded, while the page router decodes them into route params. A request that spells a slash as %2F can therefore render a page through a catch-all route without the route rules configured for the path it resolves to. The fix for [GHSA-6gq8-jgmh-3ffp](https://github.com/nuxt/nuxt/security/advisories/GHSA-6gq8-jgmh-3ffp) deliberately left reserved escapes such as %2F encoded, so it did not cover this form. ### Impact An unauthenticated attacker can bypass route rules that protect paths served by a catch-all page route, or by a custom route whose param can span several segments. ```ts export default defineNuxtConfig({ routeRules: { '/docs/internal/**': { appMiddleware: 'auth', headers: { 'X-F…

Security Severity: High CVE-2026-128118 GHSA-M9J8-JCMV-HP69

SvelteKit: Build-time server-only module import guard could fail, resulting in server secrets being statically replaced in client bundle

GitHub Advisories

Under certain circumstances, server-only imports, which typically cannot be included in the client bundle, could make their way into it, potentially exposing secrets. This could only occur when those server-only imports were made through src/params.js.

Security Severity: High CVE-2026-128120 GHSA-3R8G-JCQQ-3P5J

SvelteKit: DoS while parsing form data from a remote functions `form`

GitHub Advisories

This only affects applications using the experimental remote functions flag and utilizing the form, query, or command remote functions. A specially-crafted request could block the event loop for extended periods of time during parsing.

Security Severity: High CVE-2026-128124 GHSA-JM3W-GW2P-XJFJ

AIOHTTP: Event loop stall in add_domain() wildcard matching

GitHub Advisories

### Summary Application.add_domain() compiled each * in a host mask to [^:]*. With two or more wildcards in a mask, matching a long Host header that does not match the mask took polynomial time on the event loop. ### Impact An attacker could stall a server that registers a domain mask with more than one wildcard by sending requests with a long Host header. ### Workaround Use at most one * in a domain mask. --- Patch: https://github.com/aio-libs/aiohttp/commit/c6ac0e44c3c573ff9616f4a6a532992538b31e43

Security Severity: Medium CVE-2026-128125 GHSA-5PV8-VVHC-H7JV

AIOHTTP: Unbounded cookie storage in client CookieJar

GitHub Advisories

### Summary Set-Cookie parsing created additional cookies from unrecognised name=value attributes, and CookieJar had no limit on the number of cookies stored or sent. A server could make the client store a very large number of cookies and generate very large Cookie headers. ### Impact A malicious server could cause excessive memory and CPU use in a client, repeated on every redirect, and cause later requests to the same domain to build an excessively large Cookie header. --- Patch: https://github.com/aio-libs/aiohttp/commit/6963ee0befec1502b6bb7b4db6c72d044c08f4fa

Security Severity: High CVE-2026-128126 GHSA-XGW8-8CCX-RMQH

AIOHTTP: Too many URL-encoded form fields block the event loop

GitHub Advisories

### Summary Request.post() had no limit on the number of fields in a URL-encoded form body. Inserting a large number of repeated keys into a MultiDict took quadratic time on the event loop. ### Impact An attacker could block the event loop with a form POST within the default client_max_size to any handler that calls Request.post(). --- Patch: https://github.com/aio-libs/aiohttp/commit/615fec3d4f088f30d2ee72cad760152e92aa1c53

Security Severity: High CVE-2026-128127 GHSA-24C4-3P7V-29CM

AIOHTTP: Base64 multipart parts bypass client_max_size

GitHub Advisories

### Summary When reading a multipart part with Content-Transfer-Encoding: base64, BodyPartReader.read_chunk() kept reading until the chunk length was a multiple of 4, with no byte limit. A part with a short Content-Length, or a long run of whitespace, could cause the entire remaining body to be read into memory within a single call before any size check, or spin on the event loop. ### Impact An attacker could bypass client_max_size to cause excessive memory use, or block the event loop, with a specially crafted multipart request to any handler that reads multipart data. --- Patch: https://github.com/aio-libs/aiohttp/commit/a555ab698e08e9baea7386d5b4c0761cb8956fdd

Security Severity: High CVE-2026-128128 GHSA-3RP8-RXJ8-MVJW

AIOHTTP: WebSocket max_msg_size bypass via integer overflow

GitHub Advisories

### Summary The max_msg_size check in the WebSocket reader added the declared frame length to the size of the partial message already buffered. In the C extension this addition is 64-bit arithmetic, so a declared length close to 2**63 overflowed and the check passed. ### Impact An attacker could bypass max_msg_size and cause unbounded memory use by streaming an oversized WebSocket message after a small non-final fragment. ### Workaround If unable to upgrade, the Python reader is unaffected and can be used with AIOHTTP_NO_EXTENSIONS=1. --- Patch: https://github.com/aio-libs/aiohttp/commit/8cfbe9abe5e11b84006a10f9bdf82bf607671dab

Security Severity: High CVE-2026-128129 GHSA-PW86-H8FM-J323

AIOHTTP: Unbounded buffering of data received during an upgrade request

GitHub Advisories

### Summary While a request flagged as an upgrade (e.g. a WebSocket handshake) was being handled, all further data received on the connection was buffered with no size limit or flow control until the handler completed. ### Impact An attacker could cause unbounded memory use by streaming data behind an upgrade request to any handler that does not immediately accept or reject the upgrade. --- Patch: https://github.com/aio-libs/aiohttp/commit/3d850ee9b92573c7e913821cbcb96005beb3f4df

Security Severity: High CVE-2026-128130 GHSA-28QF-CPWQ-VMC2

AIOHTTP: Pure-Python parser request replay and buffer growth behind a declined upgrade

GitHub Advisories

### Summary When the pipelined request queue was full, the pure-Python parser stored the unparsed remainder internally and also returned it to the caller. After a handler declined an upgrade request, the buffered data was re-fed, so the buffer grew with each handled request and already-handled requests were dispatched to the application again. ### Impact If users are using the Python parser (AIOHTTP_NO_EXTENSIONS, or not a standard wheel installed), an attacker could cause excessive memory use and cause pipelined requests to be processed more than once. ### Workaround Switch to the default C parser. --- Patch: https://github.com/aio-libs/aiohttp/commit/47babd8c23ca79e2bae6cc8dcb5752b61e369fc7

Security Severity: High CVE-2026-128131 GHSA-H4CC-HM5H-FMM9

AIOHTTP: Concatenated compressed streams cause excessive CPU use

GitHub Advisories

### Summary When decompressing a payload made up of many concatenated compressed members (gzip, deflate or zstd), each member was decoded by passing the entire remaining input to a new decompressor, resulting in quadratic CPU time. Empty members produce no output, so client_max_size and output backpressure did not limit the work. ### Impact An attacker could block the event loop of a server with a specially crafted compressed request body or WebSocket message. A malicious server could do the same to a client. --- Patch: https://github.com/aio-libs/aiohttp/commit/d925a80539ffd227da1d93ab4a5bff123cc777db

Security Severity: High CVE-2026-128132 GHSA-5RMC-48H2-HVCM

AIOHTTP: WebSocket receive queue limits bypassed by small or compressed messages

GitHub Advisories

### Summary The WebSocket reader continued parsing frames already received after the receive queue had paused the transport, and empty messages were not counted towards the queue size. With permessage-deflate, a single read of compressed frames could add many megabytes of decompressed messages to the queue. ### Impact An attacker could cause excessive memory use in a WebSocket server, or a malicious server against a client, by sending many small or compressed messages faster than the application consumes them. --- Patch: https://github.com/aio-libs/aiohttp/commit/0ae507423f681161efa77d20052b4054397c7fb6

Security Severity: Medium CVE-2026-128119 GHSA-6CF5-GC4Q-FM3X

SvelteKit: Private `query.batch` functions could collide, producing unexpected parameter / function combinations

GitHub Advisories

Under certain circumstances, private (non-exported) query.batch functions could end up sharing a batch, resulting in the arguments from one function being passed to another. This only affects apps using the experimental remote functions flag and non-exported query.batch functions.

Security Severity: Medium CVE-2026-128116 GHSA-RQP5-R3WG-VG35

SvelteKit: Protocol-relative module import during server-side route resolution allows cross-origin script execution

GitHub Advisories

If an attacker could, using some form of social engineering or other exploit, get a user to use client-side navigation to navigate to a specially-crafted link, the attacker could cause code from another domain to be imported and run on the user's machine. This only affected apps with router.resolution: 'server'.

Security Severity: Medium CVE-2026-126302 GHSA-XMFG-F9CM-W86Q

NLTK: Symlink escape in chat80.sql_query bypasses the pathsec data-root sandbox to read out-of-root SQLite databases

GitHub Advisories

## Summary nltk.sem.chat80.sql_query() opens a SQLite database by handing the result of nltk.data.find(dbname) straight to sqlite3.connect() without the path-containment check that the NLTK data sandbox (nltk.pathsec) is meant to enforce. nltk.data.find() applies only lexical checks to the resource name and returns a FileSystemPathPointer whose path is normalized with os.path.abspath but never resolved for symlinks. As a result, an in-root symbolic link that points at a SQLite file outside every registered NLTK data root is followed by SQLite, and the caller receives query results from the out-of-sandbox database. An attacker who can place a file inside a directory the application trusts as an NLTK data root can read SQLite databases that the pathsec sandbox is supposed to k…

Security Severity: Medium CVE-2026-126296 GHSA-59F9-GQG8-MQPJ

NLTK: Path Traversal in save_maxent_params / load_maxent_params Allow Arbitrary File READ/WRITE

GitHub Advisories

### Summary Path traversal in NLTK's save_maxent_params() and load_maxent_params() allows arbitrary file write and arbitrary file read outside the directories permitted by NLTK's pathsec security mechanism. This vulnerability was previously reported through Huntr, accepted by the NLTK project, and assigned CVE-2026-15367. A $750 bounty was paid through Huntr (i didnt get the fix bounty). Huntr subsequently shut down its OSS vulnerability program, so I am submitting this report through GitHub to continue the existing disclosure process and preserve the original CVE assignment and researcher credit. ### Details The affected functions are: - nltk.classify.maxent.load_maxent_params() - nltk.classify.maxent.save_maxent_params() Both functions construct filesystem paths from the caller-controll…

Security

Google Finds Hackers Using AI Agents to Build and Run Exploits From Software Patches

The Hacker News

Google on Monday revealed that adversarial use of artificial intelligence (AI) by threat actors has gone beyond manual prompting to deploying autonomous multi-agent offensive frameworks like ARTEX, CAIRN, CyberStrikeAI, and PentAGI to execute multi-stage intrusions at greater operational velocity. In tandem, threat actors are leveraging the power and capabilities of large language models (LLMs)

Security

⚡ Weekly Recap: N-able 0-Days, Windows 0-Days, Chrome 0-Days, Fridge 0-Days, and More Bad Days

The Hacker News

A default password opened doors it never should have. A trusted update delivered malware. Even a security feature became a way to break in. Different stories, same problem: the things meant to protect us aren't always doing their job. Meanwhile, AI is making bug hunting faster, old flaws are still paying off, and attackers keep finding easy ways in. Some attacks take real skill. Others barely

Security

Six Unpatched Danfoss Refrigeration Controller Flaws Could Allow Remote Takeover Without Login

The Hacker News

Six flaws in Danfoss AK-SM800A refrigeration controllers could let a remote attacker take over a controller without logging in, Dutch security consultancy Midnight Blue said earlier this week. No patch is available, and the researchers say the newest firmware, version 5.4.0, does not fix the flaws. Government cybersecurity agencies in Belgium, Ireland and Germany told operators this week to

Security

Retadup Worm Resurfaces 7 Years After Takedown to Spread CoffeeLoader Malware

The Hacker News

Cybersecurity researchers have disclosed details of a new variant of CoffeeLoader, a malware designed to deliver additional payloads to infected machines. "On launch, the NSIS-based installer executable dropped a file named '7z.dll' into a temporary directory and ran it through rundll32.exe," Kaspersky said in an analysis published today. "The '7z.dll' file was a patched version of the

Security

SANSAR Linux Cryptomining Malware Uses Modified NVIDIA Library to Hide GPU Activity

The Hacker News

A financially motivated threat activity cluster tracked as REF3364 has been attributed to a Linux-focused cryptocurrency mining operation that tampers with the readings used to detect high GPU workloads. Central to the intrusion is a toolkit called SANSAR, a Rust-based orchestrator that receives commands over the TOR anonymity network to manage CPU and GPU miners. The activity was observed in

Security

Amazon Uncovers AI Agent Campaign Targeting LiteLLM, Dify, and Other Apps for API Keys

The Hacker News

Attackers' AI agents have been hunting for weak spots in internet-exposed AI apps such as LiteLLM, One API, and Dify to steal the AI provider keys stored inside, according to the agents' own records. The records, which Amazon's threat intelligence team captured with decoy servers, describe stolen keys being used to run the AI models that powered the search for more keys. The team said this

Security

BO Team Exploits Log4Shell in VMware vCenter, Compromises Russian Firm's Code-Signing Server

The Hacker News

An investigation into suspicious activity within a Russian software developer's network has uncovered a months-long compromise of its development infrastructure and a software code-signing server. The activity, documented by Kaspersky's ICS CERT team after it was contacted by the affected developer in June 2025, has been attributed to a threat actor named BO Team (aka Black Owl, Hoody Hyena,

Security

Italy Fines Meta €805 Million Over Facebook's Android Gallery Access Without Explicit Consent

The Hacker News

Meta was fined €805 million in Italy yesterday over a Facebook for Android feature that suggests photos and videos from users' phone galleries for them to post. The Garante, Italy's data protection authority, found that the feature was enabled by default and that the app accessed Italian users' photos, videos, and related metadata without their explicit consent. The company has 60 days to

Security

Stolen Fireworks AI Key Led to Cursor Data Breach and Trojanized Claude Code Extension

The Hacker News

The compromise of Anthropic's official Claude Code extension on Cursor's extension marketplace was the result of the theft of an access key that was exposed in the wake of a breach targeting Fireworks AI. "An attacker obtained an access key we had issued to Fireworks," Cursor said in a Friday update. "The key was exposed by Fireworks, and the attacker used it to copy data from a read-only

Security

Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection

The Hacker News

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Friday added a high-severity security flaw impacting UnrealIRCd, an open-source Internet Relay Chat (IRC) server, to its Known Exploited Vulnerabilities (KEV) catalog, following reports of active exploitation. The vulnerability, tracked as CVE-2026-114713 (CVSS score: 8.6), is a case of improper neutralization of delimiters

Security Severity: High CVE-2026-126299 GHSA-89P3-FCCH-88PH

NLTK: Quadratic-time CPU denial of service in CCG lexicon parser (fromstring) on wide bracket bodies and operator chains

GitHub Advisories

## Summary The public CCG lexicon parser nltk.ccg.lexicon.fromstring parses caller-influenced lexicon text with two pure-Python loops whose cost is quadratic in the input width. A service that parses an untrusted CCG lexicon string can be driven into tens of seconds of single-threaded CPU by a few-megabyte input, starving the request worker. No authentication or user interaction is required. ## Root Cause matchBrackets consumes a bracket body one character at a time with inside = inside + rest[0]; rest = rest[1:]. The rest = rest[1:] tail re-slice copies the entire remaining string on every iteration, so a flat bracket body costs O(n^2). augParseCategory drives a while rest != "": operator loop that re-copies the regular-expression match tail (rest = app[3]) once per operato…

Security Severity: High CVE-2026-126298 GHSA-R53H-RW34-8H97

NLTK: Quadratic-time CPU denial of service in Tree.chomsky_normal_form right-factor binarization via list.pop(0)

GitHub Advisories

## Summary Tree.chomsky_normal_form() binarizes a parse tree and defaults to right factoring. For a node with N children the right-factor branch repeatedly removes the first element of a working list with list.pop(0), which shifts all remaining elements each time, so binarizing one wide node costs O(N^2). An application that converts an attacker-supplied treebank tree to Chomsky Normal Form can be forced into tens of seconds of single-threaded CPU by one wide flat tree. No authentication or user interaction is required. ## Root Cause In the default right-factor branch the transform executes curNode[0:] = [nodeCopy.pop(0), newNode] inside a loop over the N children of a node. list.pop(0) is O(len) because it shifts every remaining element down by one; performed N-2 times over a shr…

Security Severity: High CVE-2026-126297 GHSA-V8F3-6PHW-6MH9

NLTK: Quadratic-time CPU denial of service in ConllCorpusReader SRL instance builder via nested span rescan

GitHub Advisories

## Summary ConllCorpusReader.srl_instances() builds semantic-role-labeling instances from a CoNLL corpus block. For a sentence block with P predicates and P span columns, the instance builder rescans every span column (and every span within it) once per predicate while searching for each predicate's head, giving O(P^2 * R) work. A single well-formed block that places the head span in the last column forces the full scan on every predicate, so an application that reads an attacker-supplied CoNLL SRL corpus can be driven into tens of seconds of single-threaded CPU. No authentication or user interaction is required. ## Root Cause _get_srl_instances iterates over the P predicates of a block; for each predicate it scans every span list and every span within it, using an inner break that…

Security Severity: Medium CVE-2026-126295 GHSA-FG9W-WFP5-J933

NLTK: BllipParser passes caller-supplied model paths to the bllipparser C extension with no pathsec check, enabling arbitrary read

GitHub Advisories

## Summary BllipParser in nltk/parse/bllip.py hands caller-supplied filesystem paths to the native bllipparser C extension without routing them through NLTK's pathsec validation. The constructor parameters parser_model, reranker_features, and reranker_weights, and the alternative from_unified_model_dir() entry point, flow directly to the C extension's load_parser_model() and load_reranker_model() calls, which open and read the given path at the OS level. Any application that passes an attacker-influenced path to this API reads a file of the attacker's choosing from anywhere on the filesystem, outside the NLTK data roots that every other NLTK tool wrapper confines access to. ## Root Cause As of NLTK 3.10.0, SECURITY.md documents a centralized I/O security module (`nlt…

Security Severity: High CVE-2026-62297 GHSA-QFX6-Q44V-9QQW

ag-psd can exhaust memory when parsing crafted PSD dimensions

GitHub Advisories

### Summary readPsd() commits the image/layer buffers from the declared header geometry (width x height x channels x depth, and per-layer rectangles) before validating those values against the actual data. A tiny crafted PSD declaring huge geometry forces a multi-gigabyte allocation. ### Impact On ag-psd 30.2.0, Node 24, a 52-byte PSD makes readPsd(buf) commit ~3.17 GB (measured peak RSS) in ~0.45 s before throwing a catchable RangeError ("Offset is outside the bounds of the DataView") — about 61,000,000x amplification. Because the buffer is committed before validation, the allocation OOM-kills the process before the error on essentially any host (uncatchable), and concurrent requests exhaust memory. Any service reading untrusted PSDs with ag-psd is exposed to a remote DoS. This is distin…

Security Severity: Low CVE-2026-62683 GHSA-PP88-JHWJ-5QH5

File Browser: Trailing-slash directory deletion leaves public shares active for recreated paths

GitHub Advisories

## Summary File Browser v2.63.15 can leave a public directory share behind when the shared directory is deleted through a path with a trailing slash. The share cleanup path calls DeleteWithPathPrefix(file.Path, userID), but the Bolt backend performs the database prefix query with the unnormalized argument before trimming the slash for boundary checks. For a stored share at /a, deleting /a/ queries for paths prefixed by /a/, so the exact /a share is never loaded and never deleted. If a directory with the same path is later recreated, the stale public share becomes active again and exposes the new directory contents through the old public URL. ## Impact An authenticated user with share, download, and delete permissions can create a valid public share, delete the shared path with a…

Security Severity: Medium GHSA-GPWC-27CW-RH9R

NLTK: Quadratic CPU exhaustion in LegalitySyllableTokenizer.tokenize via unguarded onset reversal loop

GitHub Advisories

## Summary LegalitySyllableTokenizer.tokenize in the NLTK tokenizer package contains an unguarded O(n^2) processing loop. When the method is called on a single token that consists of a long run of vowels (for example "a" * n), it consumes CPU time proportional to the square of the token length. An attacker who can supply an untrusted token to this public tokenizer API can force a single request to saturate one CPU core for a prolonged period, degrading availability of any service that syllabifies attacker-controlled text. No authentication, special configuration, or user interaction is required. ## Root Cause The method walks the token in reverse and, on every iteration after the first vowel is seen, evaluates the membership test char_lower + current_onset[::-1] in self.legal_onsets…

Security Severity: Medium CVE-2026-126301 GHSA-GPWC-27CW-RH9R

NLTK: Quadratic CPU exhaustion in LegalitySyllableTokenizer.tokenize via unguarded onset reversal loop

GitHub Advisories

## Summary LegalitySyllableTokenizer.tokenize in the NLTK tokenizer package contains an unguarded O(n^2) processing loop. When the method is called on a single token that consists of a long run of vowels (for example "a" * n), it consumes CPU time proportional to the square of the token length. An attacker who can supply an untrusted token to this public tokenizer API can force a single request to saturate one CPU core for a prolonged period, degrading availability of any service that syllabifies attacker-controlled text. No authentication, special configuration, or user interaction is required. ## Root Cause The method walks the token in reverse and, on every iteration after the first vowel is seen, evaluates the membership test char_lower + current_onset[::-1] in self.legal_onsets…

Security Severity: Medium CVE-2026-126300 GHSA-FFR9-MGRR-WCVR

NLTK: Quadratic CPU exhaustion in TreebankWordTokenizer.span_tokenize via list.pop(0) in quote-restore loop

GitHub Advisories

## Summary TreebankWordTokenizer.span_tokenize in the NLTK tokenizer package contains an unguarded O(n^2) processing loop in its quote-restoration step. When the method is invoked on text containing a long run of double-quote characters (for example '"' * n), it performs a list.pop(0) operation once per quote token, and because list.pop(0) is O(length), the total cost grows with the square of the input length. An attacker who can supply untrusted text to this public span-tokenization API can force a single request to saturate one CPU core for a prolonged period, degrading availability. No authentication, special configuration, or user interaction is required. ## Root Cause Inside span_tokenize, when the input contains double or repeated quotes, the code builds matched, a list…

Security Severity: High CVE-2026-126303 GHSA-8FX7-8JR8-84RV

NLTK: Unbounded CPU consumption in SteppingRecursiveDescentParser.parse() with ambiguous or self-embedding grammars

GitHub Advisories

## Summary nltk.parse.recursivedescent.SteppingRecursiveDescentParser.parse() performs an unbounded top-down search over ambiguous or self-embedding context-free grammars with no wall-clock or step limit. An actor who can influence the grammar and supply a short input to a caller that uses this parser can force a single parse() call to pin a CPU core indefinitely, producing a denial of service. The related base class RecursiveDescentParser gained a max_time wall-clock deadline, but the stepping subclass drives its own step loop and never arms or consults that deadline, and its constructor does not accept a max_time parameter, so the guard cannot be enabled on this path. ## Root Cause RecursiveDescentParser bounds its recursive search inside _parse: it arms a wall-clock deadl…

Security Severity: High CVE-2026-126304 GHSA-QG35-44QX-7VRR

NLTK: Symlink escape in YCOECorpusReader lets a psd/pos directory symlink read files outside the corpus root within the data sandbox

GitHub Advisories

## Summary YCOECorpusReader builds two nested corpus sub-readers whose roots are derived from self.root.join("psd") and self.root.join("pos") (nltk/corpus/reader/ycoe.py). Because FileSystemPathPointer.join() (nltk/data.py) performs a purely lexical containment check and never resolves symlinks, and because CorpusReader.__init__ (nltk/corpus/reader/api.py) validates a sub-reader root only against the global NLTK data sandbox and not against the enclosing corpus root, a directory symlink named psd or pos planted inside a YCOE corpus lets the reader anchor its nested sub-readers outside the YCOE corpus root. An attacker who controls the contents of a YCOE corpus loaded under pathsec.ENFORCE=True can make parsed_sents(), tagged_words(), and related methods return file con…

Security Severity: Medium CVE-2026-128117 GHSA-MW6W-2FMV-PVW3

SvelteKit: adapter-node crashes with an unhandled URIError when `reroute` rewrites malformed pathnames

GitHub Advisories

When reroute turned an invalid percent-encoded path into a valid path, it could potentially trigger a comparison that would crash the server.

Security Severity: Medium CVE-2026-128121 GHSA-JF9X-2FG2-HX4W

SvelteKit: Prerendered paths are interpreted as regular expressions in Vercel route config generated by @sveltejs/adapter-vercel and @sveltejs/adapter-static

GitHub Advisories

If an attacker could influence a link that was crawled during the prerender phase, that link could later be interpreted as a regex in the Vercel routing configuration.

Security Severity: Medium CVE-2026-128122 GHSA-5WG4-Q3WW-283H

SvelteKit: Prerendered redirect paths can inject arbitrary rules into the `_redirects` file generated by `@sveltejs/adapter-cloudflare`

GitHub Advisories

If an attacker can influence the links crawled during prerendering, they can influence the redirects entries that are added to the Cloudflare platform redirects generated during the adapt phase of the build.

Security Severity: Medium CVE-2026-128123 GHSA-RQW3-X7HX-MM3P

SvelteKit: `@sveltejs/adapter-node` crashes when proxying certain requests via `fetch`

GitHub Advisories

In affected versions, @sveltejs/adapter-node can attempt to add a header to an immutable request in a context that causes the server to crash, denying service to any other requests routed to that server.

Security Severity: Low CVE-2026-126347 GHSA-5CJW-F85J-CV6R

Tornado: Open redirect via triple-slash redirect paths

GitHub Advisories

### Summary Due to differences in the way browsers and Python's urllib parse urls, browsers treat a string starting with three or more slashes as a protocol-level redirect, while urllib does not. This means that the 6.6.0 fix for the RedirectHandler open redirect (CVE-2026-116578, commit cc75ab0e) is incomplete. Tornado 6.6.1 improves the open-redirect detection to handle this case correctly, as well as fixing a regression in the 6.6.0 implementation.

Hosting & Network

Kitesurf is now open source

Cloudflare

Kitesurf, our experimental browser engine for AI agents, is now open source. Inspect the code, run it locally, or deploy your own instance on Cloudflare Workers.

Security Severity: High CVE-2026-128089 GHSA-VVF4-9X63-8XVV

dnspython has excessive memory and CPU use

GitHub Advisories

### Summary A maliciously crafted zone file could use a WKS record to consume excessive memory and CPU, possibly causing the process to exit due to memory exhaustion. ### Details The from_text() parser does not check that a WKS record service number is between 0 and 65535 inclusive. It then uses this number to resize the bitmap to accommodate a bit with that offset. This can cause extremely large memory allocations, and also extends the array very inefficiently, wasting CPU. ### Proof of concept This demonstrates the failure to limit the service number, though with a value that does not cause excessive memory or CPU consumption. `` rd = dns.rdata.from_text("IN", "WKS", "10.0.0.1 udp 65536") `` ### Impact If dnspython is used to read zonefile format where the attacker can control the t…

Security Severity: Medium CVE-2026-128077 GHSA-R99W-JH2X-3MG9

Nuxt: Incomplete fix for GHSA-9v7c-q64q-vv33: a leading `//` in the request path bypasses `server/middleware` path checks and server route rules on page routes

GitHub Advisories

### Summary Since 4.6.0, Nuxt parses a request path that starts with // as a URL with a host before rendering a page, so //x/admin renders the page at /admin. Nitro's routing, Nitro's route rules and server/middleware see the path as //x/admin, so server-side checks keyed on /admin do not apply. The fix for [GHSA-9v7c-q64q-vv33](https://github.com/nuxt/nuxt/security/advisories/GHSA-9v7c-q64q-vv33) in 4.6.3 covered dot segments but not this form. ### Impact An unauthenticated attacker can bypass server-side controls that match on the request path of a page route. A route-scoped server handler is skipped: ``ts // nuxt.config.ts export default defineNuxtConfig({ serverHandlers: [{ route: '/admin', middleware: true, handler: '~~/server/admin-guard.ts' }], }) `` ```ts // serv…

Security Severity: Medium CVE-2026-128080 GHSA-3V2P-HM54-8QCQ

OpenTelemetry JavaScript: Insertion of Sensitive Information into Log File and Exposure of Sensitive Information to an Unauthorized Actor in @opentelemetry/instrumentation-http

GitHub Advisories

### Summary @opentelemetry/instrumentation-http redacts sensitive URL query parameters on **outgoing (client) spans** but not on **incoming (server) spans**. The server-span path writes the raw query string verbatim into the url.query attribute, so credentials embedded in inbound request URLs — AWS presigned-URL signatures, Azure SAS tokens (sig), GCS signed-URL signatures — are exported in plaintext to the configured tracing backend. Configuring the redactedQueryParams option **does not change this**, as this applies only to outgoing (client) spans. ### Impact **Information disclosure / credential leakage** (CWE-200; CWE-532, insertion of sensitive information into telemetry data). **Who is impacted:** any Node.js service instrumented with @opentelemetry/instrumentation-http —…

Hosting & Network

Adapting to AI penetration testing orchestrators: The Modern Security Model

Cloudflare

AI-orchestrated penetration testing platforms like ARTEX have become increasingly powerful tools enabling effective attacks on exposed infrastructure. Here we share Cloudflare’s observations and recommended countermeasures.

Security Severity: High CVE-2026-128082 GHSA-6VHM-J9H7-F9GH

AutoMapper: Uncontrolled Recursion with Constructor Parameters

GitHub Advisories

### Summary MaxDepth, whether set explicitly or applied by default (64) to self-referential type maps, was not enforced when the recursion goes through constructor parameters. Mapping a deeply nested source to a destination built through its constructor, such as a positional record, recurses without bound and throws a StackOverflowException. That exception can't be caught and terminates the process. This bypasses the mitigation for CVE-2026-32933. ### Details The type depth used by MaxDepth was incremented only after the destination object was created. Constructor parameters, including child objects of the same type, are mapped while the destination is created, so each level recursed before its parent was counted, and the depth check never tripped. Affected: - destination types ma…

Security Severity: Low CVE-2026-128087 GHSA-9264-JVGF-6W2F

russh kex_done: Shared-secret callback runs before server host-key verification

GitHub Advisories

### Summary A malicious SSH server whose host key is rejected can still cause russh's client::Handler::kex_done() callback to execute with the raw key-exchange shared secret. Applications using the callback for its documented protocol-bridging purpose may derive keys, initialize a secondary data channel, or perform another externally visible action before russh calls check_server_key() and rejects the server. ### Details During the initial key exchange, russh calls kex_done() immediately after the server proves possession of the presented host key, but before the application decides whether that key belongs to the intended server: ```rust let shared_secret = newkeys.kex.shared_secret_bytes(); handler .kex_done(shared_secret, &newkeys.names, session) .await?; // Initial KEX only chec…

Security Severity: Low CVE-2026-128088 GHSA-736F-C93Q-9FWX

russh try_sign: asynchronous confirmation can sign after agent lock

GitHub Advisories

### Summary In russh 0.65.0, a sign request for a confirmation-constrained key can retain and use the private key after another connection locks the agent. try_sign() snapshots an Arc before awaiting Agent::confirm() and does not revalidate the shared lock state after the await. An agent-forwarding peer can therefore obtain a signature while the agent is locked and every new request is being rejected. ### Details The agent's lock and key stores are shared by all connections. respond() reads the lock state once, then dispatches a sign request: ```rust let is_locked = { // ... read the shared lock ... }; // ... Some((&13, mut r)) if !is_locked && agentref.confirm_request(MessageType::Sign).await => { let agent = self.agent.take().ok_or(Error::AgentFailure)?; let (agent, signed) =…

Security Severity: Medium CVE-2026-128086 GHSA-RRFC-GJM9-CGRJ

OpenTelemetry-Go: Eager W3C baggage-property materialization causes bounded memory-allocation amplification

GitHub Advisories

## Summary OpenTelemetry Go eagerly materializes W3C baggage metadata into property objects during parsing. Slice growth, serialization, and copying into the internal representation cause **bounded but disproportionate memory-allocation amplification** for a valid, densely populated header. In v1.46.0 and v1.47.0-rc.1, the 8,192-byte raw-input limit is checked before member parsing; this is not unlimited allocation or a bypass of that limit. A valid 8,191-byte value containing one member and 4,094 properties causes approximately 778 KB of cumulative allocation per parse. A corrected measurement with forced garbage collection before and after parsing retains approximately 164 KB per result while it remains live. These are different metrics: approximately 95 times the input in allocation tr…