Search: payload.bin
656 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| High | 8.7 | EPSS 0.4% | CVE-2026-111923fleetdm fleet · Uncontrolled Recursion High8.7EPSS 0.4%CVE Database V5CVE-2026-111923 Fleet versions prior to 4.89.0 have an unbounded recursion vulnerability in the Apple MDM enrollment property list parsing. This flaw allows unauthenticated attackers to send a crafted binary plist payload that triggers exponential resource consumption, causing the server to crash. The vulnerability can be exploited by sending a payload of about 150 bytes to the enrollment endpoints, leading to CPU and memory exhaustion. | CVE Database V5 | ||
| –Not rated | – | Palo Alto Unit 42 An AI-powered espionage campaign, tracked as CL-UNK-1211, targeted government and state-affiliated Linux infrastructure from October 2025 to April 2026. The attackers used AI-generated payloads, custom malware, web shells, and credential harvesting techniques to maintain persistent access and conduct reconnaissance. They deployed multiple web shells, modified PHP configurations for persistence, and used advanced anti-forensics methods including disabling endpoint protections and tampering with system logs. Credential theft was achieved through hijacked .bashrc files and PHP login page modifications. The campaign aimed to dump sensitive databases and exfiltrate government mailboxes to access social media accounts. The attackers combined open-source tools with custom cross-platform backdoors and employed AI to streamline payload creation. No specific patch or fix is mentioned. | Palo Alto Unit 42 | |||
| Medium | 6.0 | EPSS 0.4% | CVE-2026-108126temporal-proxy · Insecure Direct Object Reference Medium6.0EPSS 0.4%CVE Database V5CVE-2026-108126 Temporal Technologies, Inc.'s temporal-proxy versions 0.2.0 through 0.8.0 have an authorization bypass vulnerability due to improper binding of encrypted payloads to namespaces. The proxy selects the decryption key based on an identifier in the payload rather than the request's namespace, allowing an authorized caller for one namespace to decrypt payloads from another namespace. This does not expose new encrypted payloads to attackers nor allow modification of ciphertext. The vulnerability has a medium severity score of 6.0 CVSS v4.0. | CVE Database V5 | ||
| High | 7.5 | EPSS 0.4% | CVE-2026-78384Apache CXF · CWE-409 High7.5EPSS 0.4%CVE Database V5CVE-2026-78384 CVE-2026-78384 is a high-severity vulnerability in Apache CXF where the CompressionUtils.inflate() method decompresses attacker-controlled DEFLATE data without limiting the output size. This can cause a small crafted payload to expand to gigabytes on the heap, potentially leading to resource exhaustion. The flaw is exploitable via JWE decryption with zip=DEF and SAML redirect/POST binding token inflation, both occurring before trust validation. Fixed versions include 4.2.4, 4.1.9, and 3.6.13, which introduce a configurable maximum inflated-size cap to prevent excessive memory usage. | CVE Database V5 | ||
| –Not rated | – | AlienVault OTX General The Akira ransomware attack involved an adversary gaining initial access via Remote Desktop Protocol (RDP), disabling antivirus protections on the compromised endpoint, exfiltrating data using Rclone, and maintaining persistence with a GOST tunneling tool before deploying the ransomware payload. Key indicators of compromise include specific SHA256 hashes of malicious binaries and a command and control (C2) server IP address. This attack demonstrates tactics such as antivirus evasion, data exfiltration, and persistence mechanisms. | AlienVault OTX General | |||
| Medium | 5.9 | EPSS 0.3% | Medium5.9EPSS 0.3%CVE Database V5CVE-2026-106111 ## Summary A crafted ZIP-compressed OpenEXR image can return stale memory from a prior ImageSharp operation as decoded pixels. The ZIP decoder accepts a non-empty inflate result shorter than the EXR block's required size, then the EXR decoder reads the full expected block. This is a process-local, cross-operation information-disclosure defect. It is relevant when an application uses the shared `Configuration.Default` allocator for separate image operations and exposes pixels or output derived from a later attacker-controlled EXR decode. Whether that creates a network attack path depends on the host application. No active exploitation is known. ## Affected package and versions - Package: `SixLabors.ImageSharp` (NuGet) - Affected published releases: **4.0.0, 4.1.0, and 4.1.1** - Affected range: `>= 4.0.0, <= 4.1.1` - Commit `0815358f9202a78bc7f3b83e19282dc3654b500f` corresponds to release **v4.1.1**. EXR support first appears in v4.0.0. The cross-operation PoC exposes the prior-operation marker on each published 4.x release, while the full-inflate control does not expose it on any of them. ## Details For ZIP/ZIPS EXR compression, [`ExrDecoderCore`](https://github.com/SixLabors/ImageSharp/blob/0815358f9202a78bc7f3b83e19282dc3654b500f/src/ImageSharp/Formats/Exr/ExrDecoderCore.cs#L169-L205) allocates the expected block buffer without `AllocationOptions.Clean` and later interprets the complete buffer as channel data. [`ZipExrCompression`](https://github.com/SixLabors/ImageSharp/blob/0815358f9202a78bc7f3b83e19282dc3654b500f/src/ImageSharp/Formats/Exr/Compression/Decompressors/ZipExrCompression.cs#L25-L38) accepts a partial but non-empty inflate result: [`UndoZipCompression`](https://github.com/SixLabors/ImageSharp/blob/0815358f9202a78bc7f3b83e19282dc3654b500f/src/ImageSharp/Formats/Exr/Compression/ExrBaseDecompressor.cs#L45-L75) rejects only `totalRead == 0`. Only the returned prefix is reconstructed and interleaved into the destination block. The remaining bytes retain allocator contents from a completed prior operation. `ExrDecoderCore` then converts those bytes into returned image pixels. ## Reproduction The attached Docker PoC uses the published `SixLabors.ImageSharp` NuGet package version 4.1.1. It first completes a valid 64x1 FLOAT/ZIPS EXR encoding that contains the test value `0.27182817`. It then decodes a separate crafted 256x1 FLOAT/ZIPS EXR. The exploit payload inflates to 8 bytes although the declared image block needs 1024 bytes. The control payload inflates to all 1024 bytes. The marker is present only in exploit output. ```sh docker build -t imagesharp-4q3p-poc . docker run --rm imagesharp-4q3p-poc exploit docker run --rm imagesharp-4q3p-poc control ``` Test environment: Docker with `mcr.microsoft.com/dotnet/sdk:8.0`, .NET SDK 8.0.424 / .NET 8, Debian 12, Linux ARM64. Observed output: ```text imagesharp-assembly=4.0.0.0 informational-version=4.1.1+0815358f9202a78bc7f3b83e19282dc3654b500f mode=exploit prior-operation=valid-exr-encode-completed bytes=383 prior-value=0.27182817 leaked=True first-prior-value-pixel=4 imagesharp-assembly=4.0.0.0 informational-version=4.1.1+0815358f9202a78bc7f3b83e19282dc3654b500f mode=control prior-operation=valid-exr-encode-completed bytes=383 prior-value=0.27182817 leaked=False first-prior-value-pixel=-1 ``` ## Suggested remediation Reject ZIP/ZIPS EXR blocks unless the decompressor produces exactly the expected uncompressed byte count. Clearing the destination buffer is defense in depth, but exact-length validation is required before parsing any decompressed bytes. ### Complete PoC files Program.cs: ```csharp using System.Buffers.Binary; using System.Globalization; using System.IO.Compression; using System.Reflection; using System.Text; using SixLabors.ImageSharp; using SixLabors.ImageSharp.Formats; using SixLabors.ImageSharp.Formats.Exr; using SixLabors.ImageSharp.Formats.Exr.Constants; using SixLabors.ImageSharp.PixelFormats; // This performs two independent completed ImageSharp operations in one process. // The first is a valid EXR encoding containing a test value. The second is a // malformed EXR decode whose short ZIP result exposes that value from the // allocator shared through Configuration.Default. internal static class Program { private const int PriorWidth = 64; private const int AttackerWidth = 256; private const float PriorValue = 0.271828182f; private static int Main(string[] args) { bool exploit = args.Length == 0 || args[0] == "exploit"; if (args.Length > 0 && args[0] is not ("exploit" or "control")) { Console.Error.WriteLine("usage: final-4q3p [exploit|control]"); return 2; } Assembly imageSharp = typeof(Image).Assembly; string informationalVersion = imageSharp .GetCustomAttribute<AssemblyInformationalVersionAttribute>()? .InformationalVersion ?? "(missing)"; Console.WriteLine($"imagesharp-ass | CVE Database V5 | ||
| High | 8.8 | EPSS 0.5% | High8.8EPSS 0.5%CVE Database V5CVE-2026-97644 The Groundhogg — CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to Privilege Escalation via Contact Identity Rebinding in all versions up to, and including, 4.9 The vulnerability exists because the `create_contact` function in the v3 REST endpoint (`POST /gh/v3/contacts`) is gated solely by the `add_contacts` capability and forwards the full request payload — including the security-bearing `user_id` column — into the upsert path of `Contacts_DB::add()`, which bypasses the ownership guard that `Contacts_DB::update()` enforces, allowing an attacker to rebind any existing contact record to an arbitrary WordPress user ID. This makes it possible for authenticated attackers with Sales Representative-level access and above to upsert their own contact row to point to an Administrator's user ID, then invoke the v4 email-test endpoint (`POST /gh/v4/emails/test`) — also accessible to the Sales Representative role via the `send_emails` capability — to generate an `{auto_login_url}` one-time permissions key bound to the rebound contact, and consume that link to call `wp_set_auth_cookie()` and gain a fully authenticated session as the WordPress Administrator. | CVE Database V5 | ||
| High | 8.7 | EPSS 0.3% | CVE-2026-83663Apache Thrift · Uncontrolled Recursion High8.7EPSS 0.3%CVE Database V5CVE-2026-83663 CVE-2026-83663 is an uncontrolled recursion vulnerability in the Go bindings of Apache Thrift before version 0.25.0. The issue arises because the Go transports read frames recursively when encountering frames with no payload bytes, leading to unbounded recursion depth. This causes the Go runtime stack limit to be exceeded, resulting in a fatal error that terminates the entire process. The vulnerability has a high severity with a CVSS score of 8.7. Users are advised to upgrade to Apache Thrift version 0.25.0, which contains the fix. | CVE Database V5 | ||
| High | 8.7 | EPSS 0.3% | CVE-2026-83745Apache Thrift · Excessive Memory Allocation High8.7EPSS 0.3%CVE Database V5CVE-2026-83745 Memory allocation with excessive size value, Improper handling of length parameter inconsistency vulnerability in Apache Thrift nodejs and D lang bindings. Both bindings' WebSocket server transports read the payload length out of the frame header and allocate that many bytes immediately, without checking that the bytes have arrived. A single ~14-byte frame therefore commits as much memory as it cares to declare -- measured at 513 MiB against the Node.js server and 2 GiB against the D transport -- and in the Node.js case the connection is left open afterwards, so the frame can simply be sent again. This issue affects Apache Thrift before 0.25.0. Users are recommended to upgrade to version 0.25.0, which fixes the issue. | CVE Database V5 | ||
| Critical | 9.5 | KEVEPSS 81% | Critical9.5KEVEPSS 81%AlienVault OTX GeneralCVE-2026-88771 CVE-2026-88771 is a critical pre-authentication command injection vulnerability in Citrix NetScaler ADC and Gateway. Exploitation involves attacker-controlled usernames triggering command execution, payload retrieval, reverse shell deployment, web shell installation, privileged account creation, and attempted exfiltration of configuration data. Two second-stage payloads, main.py and update_c08937.pl, facilitate persistent access and data theft. Post-exploitation artifacts include creation of superuser accounts and system binary modifications. Public exploit code is available via Metasploit. No patch or remediation details are provided. | AlienVault OTX General | ||
| Critical | 9.1 | EPSS 0.7% | CVE-2026-92966Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress · Code Injection Critical9.1EPSS 0.7%CVE Database V5CVE-2026-92966 The The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 5.7.0. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes. The payload is planted during the unauthenticated booking flow and triggered when the Customer Cabinet block rendered by render_customer_dashboard() outputs the stored name into the content stream, where WordPress core's do_shortcode filter at priority 11 re-parses and executes it. | CVE Database V5 | ||
| High | 8.5 | EPSS 0.1% | CVE-2026-102566OpenNMT CTranslate2 · Out-of-bounds Write High8.5EPSS 0.1%CVE Database V5CVE-2026-102566 CTranslate2 before 4.8.1 contains a heap-based buffer overflow in the binary model loader that fails to validate payload length against allocated buffer size. Attackers can craft malicious model files with oversized payload lengths to write past heap allocation boundaries, causing crashes or arbitrary code execution. EPSS 0.1%Vulnerability | CVE Database V5 | ||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (37cd33c0908189c0085fba153be1c42776411968aa5ad652dd7ffdef88b318bc) hardhat-zet@2.0.1 is published under a name that impersonates the Hardhat Ethereum tooling ecosystem, but its README, type definitions and docs/ tree are copied verbatim from the unrelated `pino` logger project (badges and links point at npmjs.com/package/pino and github.com/pinojs/pino). The exported `middleware` in index.js is a no-op Express middleware and matches neither the `hardhat-zet` name nor the pino README. The package's declared main (index.js) top-level-requires./lib/config, which is not a configuration file but a 4,498,609-byte obfuscator.io-style bundle: a 26,113-entry rotated string array behind two runtime decoders (functions v and F), hex-encoded identifiers, and control-flow flattening. All strings and destination URLs are hidden behind the decoders, so this code runs automatically on any `require('hardhat-zet')` and its behavior is not observable without deobfuscation. Publisher metadata (author 'Robert King <hello@jsonspack.com>', bugs URL https://jsonspack.com/issues) ties to neither the Hardhat nor the pino identity. The combination — ecosystem-typosquat name targeting crypto/Hardhat developers, cover-story README lifted from an unrelated popular package, no-op public API, and a multi-megabyte obfuscated payload auto-executed on import — is the shape of a supply-chain stealer aimed at Ethereum developers. ## Source: ghsa-malware (781273d2c802d3781fecccd4434ba418c93ce88edf920b2a1163dbacf7576254) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database The nebulaai-sdk npm package version 1.0.0 contains malicious code that executes a hidden Windows executable during installation on Windows systems. This executable is disguised as a legitimate Windows console host binary and establishes a remote command-and-control connection. The package lacks legitimate SDK functionality and solely serves to deploy and run this malicious payload, resulting in arbitrary code execution under the installing user's context. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database The npm package nebula-sdk versions 1.0.0 and 1.0.1 contains malicious code embedded in its preinstall lifecycle script. This script decodes and decompresses a hidden Windows executable, which is then written to the local app data directory masquerading as a legitimate system binary and executed without user interaction. The payload is linked to a remote access trojan (RAT) tool, enabling attacker-controlled native code execution on the affected Windows machine. Installation of this package results in a full compromise of the host system. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (42d10ba1427af01794dfb0a6b39a05f969547455e9d86d75f18601b1d035c507) preinstall.js runs unconditionally on npm install and POSTs a JSON payload to a hardcoded Pipedream collector at https://f5778d1d81cc30c39dcdd0da5ca1d49a.m.pipedream.net. The payload includes os.hostname(), os.userInfo() username, platform/arch/node version, process.env.INIT_CWD, process.cwd(), the consumer project's package.json name and version, whether the consumer declares an @alphaspace dependency, npm registry hosts parsed from ~/.npmrc, CI-related environment variable names, and proxy host configuration. The same script performs DNS resolution against a hardcoded list of *.yahoo.com and *.ouryahoo.com internal hostnames (including istio-system.prod1-gq1.omega.yahoo.com and buildr.corp.yahoo.com), and for any banana.stand.*.yahoo.com name that resolves it issues an https.request with rejectUnauthorized:false, capturing the response status, Server header, and first 512 bytes of the body and forwarding them in a banana_proof field of the exfil payload. The @alphaspace scope name and an in-file 'authorized security research' banner form a dependency-confusion lure aimed at Yahoo internal builds; the installer-side behavior — host fingerprinting, npmrc/registry disclosure, and TLS-verification-disabled internal-network probing from the installer's host — fires against any machine that resolves this package. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f49ee5bcbcb7e8f1028de4021134fdbbc895e737700cf82a834fb26d3b23dd05) postinstall.js fetches an opaque binary from https://mkicom.com/.well-known/pki-validation/ct_dn8, writes it to /tmp/.nc, chmods it 0755, and launches it detached via `spawn('/bin/sh', ['-c', 'setsid ' + OUT + '... &'], {detached:true})`. The download URL is disguised under a `.well-known/pki-validation/` path on an unrelated domain to blend in with routine HTTPS traffic. index.js is an empty stub (`module.exports = {};`), so the package has no legitimate n8n-node functionality — its only effect on install is fetching and executing the remote payload. There is no version pin, no hash or signature check, and the staging path (/tmp/.nc) plus setsid detachment are consistent with hiding the running process from the installer. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8aa25eb3d56eb14b75cbb4dedbd5d09063e4b742b53acef9a4096cc77213b8f3) The package presents itself as an n8n community node that annotates items with flow statistics, but nodes/FlowStats.node.js contains two independent attacker-benefiting mechanisms. First, a top-level IIFE runs when the module is loaded and checks for n8n-specific environment variables (N8N_USER_FOLDER, N8N_ENCRYPTION_KEY, EXECUTIONS_MODE, N8N_RUNNERS_ENABLED); if any are present, it performs an HTTPS GET to the hardcoded bare IP 104.21.3.16 with a spoofed Host header of mkicom.com and rejectUnauthorized disabled, writes the response body to /tmp/.fs_dev or /tmp/.fs_prod, chmods it 0755, and spawns it detached via /bin/sh with setsid. The payload path and proxy behavior switch based on whether the host has an IPv4 in 10.0.2.0/24, indicating dev-vs-prod target discrimination. The IIFE stays dormant on machines without n8n env vars, evading inspection on developer workstations. Second, the node's execute() reads cmd and k fields from item.json.query or item.json.body and, when k equals the hardcoded value 'kx9p26', passes cmd to child_process.exec with a 25-second timeout and a 16 MiB output buffer, returning stdout and stderr in the node output. Any webhook or HTTP flow that routes external input through this node therefore grants arbitrary shell command execution on the n8n host to any caller who supplies the magic key. Neither behavior is part of the advertised statistics functionality. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (4135dd91724bdca6fc36f3a49906d219acc67afde7802cb1bd114d128984ca3d) The package's postinstall hook runs `node./loader.js`, which base64-decodes an ~8 KB embedded blob, XOR-decrypts it with a hardcoded 32-byte key, and pipes the resulting bytes into a detached, window-hidden `python -c -` child process via stdin. The loader also silently `pip install`s `requests` if missing. The advertised library surface in `index.js` is an explicit stub whose `connect()` throws, and `package.json` restricts installation to `os: ["win32"]`, so the tarball has no functional wallet-adapter behavior — its only effect on install is to execute the obfuscated Python payload on a Windows developer's machine. The combination of a hidden opaque payload, XOR-obfuscated delivery, detached hidden Python execution at `npm install` time, an inert cover-story main module, and OS pinning to Windows is a targeted install-time dropper. | GCVE Database |
Page 2 of 33 · 1 duplicate CVE record merged