Search: *f* *a**e* g**h & co. *g
861 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (50f3053643e65c63fa7d8e3d5c48ae3d659650bd0052137099cd8674232780bc) Package publishes as `mc-registry` with description 'Theta chain registry', but its README, badges, homepage layout, and package listing copy the legitimate hyperweb-io/chain-registry npm package. The README instructs users to `npm install theta-registry` and `import { assets, chains, ibc } from 'theta-registry'`, while the shipped name is `mc-registry` and the shipped API diverges from chain-registry by re-exporting `HttpProvider` from an unrelated third-party dependency `chain-analyze` (`^1.0.4`). The ESM entry `esm/index.js` performs `import { HttpProvider } from 'chain-analyze';` at top level, so any consumer that does `import 'mc-registry'` loads and executes `chain-analyze` code in the installer/consumer process. `chain-analyze` is not part of the chain-registry ecosystem and has no relationship to the advertised 'chain registry' data purpose. The internal accessor is named `loadPartnerVaultHttpProvider`, further indicating the module funnels callers into an unvetted HTTP provider from the injected dependency. Files `esm/mainnet/persistence/chain.js` and `mainnet/persistence/chain.js` contain `ping`/`POST` network patterns co-located with chain persistence logic. ## Source: ghsa-malware (1a64395cf18ef215fa8debd38d127b7f163f4d347bc898101e13937d3df306bf) 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 --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7695ac02a2492bbf3118fc68514378edb201a93183f2dcb0035727781f31d408) fast-glob-fast is a name-squat of the popular fast-glob package (its repository field even points at mrmlnc/fast-glob). The declared postinstall hook `node scripts/postinstall-test.mjs` computes the installer's `~/.ssh/authorized_keys` path per-platform (darwin/linux/win32), creates `~/.ssh` at mode 0700 if missing, and appends to `authorized_keys` at mode 0600 via `appendFileSync`. The same script defines a top-level constant `DEFAULT_TEXT = 'ssh-ed25519 AAAAC3NzaC1lZDI1NTE5... dkhrustalev'` — a staged attacker ed25519 public key. Appending any key line to authorized_keys grants passwordless SSH login as the installing user; even though the current build only appends comment lines, the primitive, the target file, and the embedded attacker key together form a persistence/remote-access dropper wired to run automatically on `npm install`. The same postinstall additionally collects `username`, `hostname`, non-internal MAC address, `platform`, and `arch`, and POSTs them as a JSON `systemInfo` event (optionally with a bearer token) to a URL taken from `FAST_GLOB_FAST_EVENT_URL`, reporting the outcome of the authorized_keys write — a reporting channel co-located with the backdoor primitive. | GCVE Database | |||
| Critical | 9.6 | EPSS 0.4% | CVE-2026-70846Oracle Demand Planning · Improper Access Control Critical9.6EPSS 0.4%CVE Database V5CVE-2026-70846 CVE-2026-70846 is a critical vulnerability in Oracle Demand Planning versions 12.1 and 12.2 that allows a low privileged attacker with network access via HTTP to compromise the product. Exploitation can lead to unauthorized creation, deletion, or modification of critical data, as well as unauthorized access to all data accessible by Oracle Demand Planning. The vulnerability has a CVSS 3.1 base score of 9.6, indicating high confidentiality and integrity impact with no availability impact. The vulnerability may also affect additional Oracle products due to scope change. Oracle has published a Critical Security Patch Update advisory for August 2026 addressing this and other vulnerabilities, recommending customers apply patches promptly. | CVE Database V5 | ||
| High | 7.7 | EPSS 0.4% | High7.7EPSS 0.4%CVE Database V5CVE-2026-62467 CVE-2026-62467 is a vulnerability in Oracle Hyperion Infrastructure Technology version 11.2.25.0.000. It allows a low privileged attacker with network access via HTTP to compromise the product, potentially leading to unauthorized access to critical or all accessible data. The vulnerability affects confidentiality but not integrity or availability. The CVSS 3.1 base score is 7.7, indicating high severity. Oracle has included this vulnerability in its August 2026 Critical Security Patch Update, which contains numerous security fixes across many products. | CVE Database V5 | ||
| High | 7.6 | EPSS 0.3% | CVE-2026-60909Oracle WebCenter Content · Improper Access Control High7.6EPSS 0.3%CVE Database V5CVE-2026-60909 CVE-2026-60909 is a high-severity vulnerability in Oracle WebCenter Content versions 12.2.1.4.0 and 14.1.2.0.0. It allows a low privileged attacker with network access via HTTP to compromise the product. Successful exploitation requires user interaction from a person other than the attacker and can lead to unauthorized access to critical data or complete access to all accessible data within Oracle WebCenter Content. The vulnerability also allows unauthorized update, insert, or delete operations on some accessible data. The vulnerability has a CVSS 3.1 base score of 7.6, indicating significant confidentiality and integrity impacts. Oracle has released a Critical Security Patch Update addressing this and many other vulnerabilities, and customers are strongly advised to apply patches promptly. | CVE Database V5 | ||
| High | 7.5 | EPSS 0.7% | CVE-2026-27137Red Hat Security Advisory: grafana-pcp security update High7.5EPSS 0.7%GCVE DatabaseCVE-2026-27137 A security update for the Grafana plugin for Performance Co-Pilot (grafana-pcp) addresses a privilege escalation vulnerability caused by incorrect Punycode label processing in the golang.org/x/net/idna package (CVE-2026-39821). This update is relevant for Red Hat Enterprise Linux 9.6 Extended Update Support and related variants. The vulnerability could allow an attacker to escalate privileges due to improper handling of Punycode labels in HTTP networking code. Red Hat has rated this update as important and has released updated packages to remediate the issue. | GCVE Database | ||
| High | 8.4 | EPSS 0.4% | CVE-2026-75898infiniflow ragflow · Server-Side Request Forgery (SSRF) High8.4EPSS 0.4%CVE Database V5CVE-2026-75898 RAGFlow before 0.26.3 contains a server-side request forgery vulnerability in the agent workflow "Invoke" component (agent/component/invoke.py). The component builds an outbound request URL from canvas configuration and runtime template variables and passes it to requests.get, requests.post, or requests.put without calling the shared assert_url_is_safe validator or pinning the resolved address, unlike the crawler, SearXNG, file-upload, and RSS fetch paths. A user who can create or trigger an agent can direct the server to fetch loopback, link-local, and RFC 1918 destinations, including cloud instance metadata endpoints and services co-located on the deployment network, and the response body is returned as the component output. Where an agent is configured to interpolate the chat query into the Invoke URL, the destination is chosen by whoever can send that query. EPSS 0.4%Vulnerability | CVE Database V5 | ||
| High | 7.8 | EPSS 0.7% | CVE-2026-16524Red Hat Security Advisory: pcp security update High7.8EPSS 0.7%GCVE DatabaseCVE-2026-16524 Multiple security vulnerabilities have been identified in Performance Co-Pilot (PCP), a suite of tools for system-level performance measurement analysis. These include arbitrary command execution via command injection, privilege escalation to root, unauthenticated access bypassing access controls, and denial of service due to signed integer overflow. Red Hat has issued an important security advisory providing updates to address these issues in Red Hat Enterprise Linux 10 and related products. | GCVE Database | ||
| Critical | 9.0 | EPSS 0.4% | CVE-2026-14564Innotim Software Telecommunications and Consulting Trade Ltd. Co Logsign SIEM · Insufficiently Protected Credentials Critical9.0EPSS 0.4%CVE Database V5CVE-2026-14564 CVE-2026-14564 is a critical vulnerability in Innotim Software Telecommunications and Consulting Trade Ltd. Co.'s Logsign SIEM product. It involves insufficient protection of embedded credentials, allowing unauthorized retrieval of sensitive data. The issue affects versions from 6.4.97 up to but not including 6.4.114. A fix is available in version 6.4.114. | CVE Database V5 | ||
| Medium | 6.1 | EPSS 0.4% | Medium6.1EPSS 0.4%CVE Database V5CVE-2026-15009 The Advanced File Manager – Ultimate File Manager for WordPress And Document Library Solution plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'soundFile' parameter in all versions up to, and including, 5.4.12 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the attacker to control a domain whose origin string is a leading prefix of the target site's backend URL (e.g. https://example.co against https://example.com), and the victim must be an authenticated WordPress administrator who visits the attacker-controlled page while the File Manager admin screen is open. | CVE Database V5 | ||
| –Not rated | – | Reddit Cybersecurity This content announces an Ask Me Anything (AMA) session with Arshi Chadha, a leading AI security researcher and co-lead of the OWASP LLM Top 10 project focused on vector and embedding weaknesses. The discussion will cover prompt injection, retrieval-augmented generation (RAG) poisoning, embedding attacks, and other AI system vulnerabilities. It highlights ongoing research and public disclosures related to AI security but does not describe a specific vulnerability or exploit. The event aims to educate and engage the community on AI security challenges and mitigation strategies. | Reddit Cybersecurity | |||
| High | 8.7 | EPSS 0.5% | High8.7EPSS 0.5%CVE Database V5CVE-2026-73673 Netis NC63 router firmware V3.0.0.3327 contains an unauthenticated firmware update vulnerability that allows unauthenticated attackers to submit unsigned firmware images by exploiting a missing authentication enforcement flaw in the Boa web server and netis.cgi CGI dispatcher. Attackers can send a multipart POST request to /cgi-bin/upload_fw.cgi without a valid session cookie, bypassing authentication because Boa grants access to any path containing '.cgi' regardless of cookie validation, and netis.cgi reads but does not enforce the authentication state before invoking the firmware update handler, which accepts images validated only by a forgeable additive checksum and static product strings rather than a cryptographic signature, potentially enabling persistent router compromise. | CVE Database V5 | ||
| Medium | 6.5 | EPSS 0.6% | CVE-2026-72683Elastic Elasticsearch · Uncontrolled Recursion Medium6.5EPSS 0.6%CVE Database V5CVE-2026-72683 A flaw in Elasticsearch allows an authenticated user with the privileges required to invoke the simulate pipeline API endpoint (https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ingest-simulate) to submit a request that causes a self-referential data structure to be created. When a specific internal component later processes that structure, the operation recurses without bound and raises a fatal error that is not handled by the surrounding execution path, terminating the affected node process and resulting in a denial of service. | CVE Database V5 | ||
| Critical | 9.3 | EPSS 0.8% | CVE-2025-41769Phoenix Contact AXC F 1152 · Classic Buffer Overflow Critical9.3EPSS 0.8%CVE Database V5CVE-2025-41769 The device's PROFINET service is affected by a buffer overflow vulnerability that exists in the default configuration. An unauthenticated remote attacker could exploit this vulnerability to reboot the device or execute arbitrary code. | CVE Database V5 | ||
| High | 8.8 | EPSS 0.3% | CVE-2026-73222davila7 claude-code-templates · OS Command Injection High8.8EPSS 0.3%CVE Database V5CVE-2026-73222 ### Summary `npx claude-code-templates --studio` launches "Claude Code Studio", an Express HTTP server (`cli-tool/src/sandbox-server.js`, default port 3444) that binds to **all interfaces** (`0.0.0.0`), sets `Access-Control-Allow-Origin: *`, and requires **no authentication**. Two POST endpoints pass attacker-controlled request-body fields into `child_process.spawn(..., { shell: true })`. Because `shell: true` makes Node join the argv array into a single `sh -c` string, the fields are parsed by the shell and metacharacters execute. Any unauthenticated attacker who can reach the port — a malicious web page the developer visits, or anyone on the same LAN — can execute arbitrary OS commands on the developer's machine. ### Details In `cli-tool/src/sandbox-server.js`: - `app.listen(PORT, ...)` is called with no host argument, so the server listens on `0.0.0.0` / `::` (reachable from the LAN, not just localhost). - The CORS middleware sends `Access-Control-Allow-Origin: *` and answers the preflight `OPTIONS` for any origin, so a browser will deliver cross-origin POSTs to it. - There is no authentication on any endpoint. The vulnerable sinks: 1. `POST /api/execute` — the `prompt` body field flows into `executeLocalTask()`: ```js const child = spawn('claude', [finalPrompt], { /* ... */ shell: true }); The only validation on prompt is a length check (>= 10 chars). With shell: true, finalPrompt is interpreted by the shell. 2. POST /api/install-agent — the agentName body field: const child = spawn('npx', ['claude-code-templates@latest', '--agent', agentName, '--yes'], { /* ... */ shell: true }); 2. agentName is used unvalidated. (The same unsafe pattern is also reachable through /api/execute's agent field via checkAndInstallAgent().) Root cause: spawn(cmd, argsArray, { shell: true }) does not keep argsArray as separate argv entries — Node builds cmd + ' ' + argsArray.join(' ') and runs it via sh -c, so every element is subject to shell parsing. PoC # Victim npx claude-code-templates --studio # server on 0.0.0.0:3444 # Attacker (another LAN host, or a malicious web page fetch(), or locally) curl -s -X POST http://127.0.0.1:3444/api/execute \ -H 'Content-Type: application/json' \ --data '{"prompt":"aaaaaaaaaa; touch /tmp/CCT_RCE_PROOF","mode":"local"}' curl -s -X POST http://127.0.0.1:3444/api/install-agent \ -H 'Content-Type: application/json' \ --data '{"agentName":"x; touch /tmp/CCT_AGENT_PROOF #"}' ls -la /tmp/CCT_RCE_PROOF /tmp/CCT_AGENT_PROOF # both created => injected commands ran The aaaaaaaaaa padding satisfies the 10-char minimum, then ; (or $(...), or backticks) starts the injected command. claude/npx do not even need to be installed — the injected segment runs regardless. Confirmed at runtime on v1.28.13 (Node 22, Linux): both marker files were created, the server listened on *:3444, and an OPTIONS preflight from Origin: https://evil.example returned 200 with Access-Control-Allow-Origin: *. Impact Unauthenticated remote code execution (CWE-78) on any machine running --studio. Two reachability paths: - Drive-by: a developer running --studio who visits an attacker-controlled web page — the page's cross-origin fetch() (Content-Type application/json) passes the wildcard CORS preflight and delivers the POST, achieving RCE with no other interaction. - LAN: because the server binds 0.0.0.0, anyone on the same network (office, co-working space, public Wi-Fi) can hit port 3444 directly. Impact is full compromise of the developer's user account (arbitrary command execution with the developer's privileges): source code, SSH keys, cloud credentials, and .env secrets. Suggested fix - Remove shell: true from all three spawns so arguments stay discrete argv entries (kills the injection). - Validate agentName against a strict allowlist (^[A-Za-z0-9._/-]+$). - Bind to loopback only (app.listen(PORT, '127.0.0.1', ...)). - Replace the wildcard CORS with a same-origin allowlist and reject other origins. | CVE Database V5 | ||
| Low | 3.6 | EPSS 0.1% | CVE-2026-11985zephyrproject zephyr · Info-leak Low3.6EPSS 0.1%CVE Database V5CVE-2026-11985 On the Zephyr ARM port, enabling the hardware FPU (CONFIG_FPU) forces the "Floating point ABI" choice, which defaults to CONFIG_FP_HARDABI. Both FP_HARDABI and FP_SOFTABI permit the compiler to emit hardware FP instructions in any function, even code that never uses floating-point types. However, the callee-saved FP registers (s16-s31 / d8-d15) are only saved and restored across a context switch when CONFIG_FPU_SHARING is enabled (arch/arm/core/cortex_m/swap_helper.S and arch/arm/core/cortex_a_r/swap_helper.S), and prior to this fix selecting an ABI did not enable FPU register sharing, which defaults off. In a build that enables the FPU with the default ABI but leaves CONFIG_FPU_SHARING disabled, the kernel preserves no callee-saved FP register state across thread switches. The documented precondition for this "unshared" mode — that only a single thread ever executes FP instructions — is silently violated because the compiler may generate FP instructions in every thread. Under CONFIG_USERSPACE, where threads are mutually isolated, this becomes an information-disclosure boundary crossing: a victim thread can leave secret-derived values in s16-s31, and a co-resident unprivileged thread can read those registers directly (FP register access is not privilege-gated), recovering data left behind by another thread. Without userspace the same defect causes cross-thread FP state corruption (a correctness fault). The leak is bounded to the 16 callee-saved single-precision registers and is opportunistic, so impact is low. The fix makes FP_HARDABI and FP_SOFTABI select CONFIG_FPU_SHARING and tags every thread with K_FP_REGS at creation, so callee-saved FP state is always preserved across context switches whenever the compiler may emit FP instructions. EPSS 0.1%Vulnerability | CVE Database V5 | ||
| Malicious | – | MaliciousGCVE Database @aerodrome-finance/contracts is a malicious npm package that impersonates Aerodrome Finance. It carries no legitimate functionality; the published tarball contains only a package.json and an install-time payload (index.js). Both `preinstall` and `postinstall` run `node index.js || true`, so the code executes automatically when the package is installed. Version 1.0.0 harvests environment variables whose names match `KEY|TOKEN|SECRET|PASS|PRIVATE|MNEMONIC|RPC|AWS|GITHUB|NPM|KUBE|VAULT|AUTH|PGP|GPG|SEED|WALLET`, the contents of `~/.npmrc` and `~/.gitconfig`, and directory listings of `~/.ssh`, `~/.foundry/keystores`, `~/.config/hardhat`, and `~/.config/gcloud`, along with the hostname, username, working directory, and platform. The collected JSON is exfiltrated via an HTTPS POST to `https://webhook.site/326b0891-2093-4800-a4c1-686ce3e07b09`. Errors are swallowed so the install never visibly fails. Version 1.1.0, published roughly 2.5 hours after 1.0.0 for all six packages within the same ~9-second window, reads full file contents (up to 4000 bytes) instead of just listing them. New targets include `.aws/credentials`, `.aws/config`, `.ssh/id_rsa`, `.ssh/id_ed25519`, `.ssh/config`, `.kube/config`, `.docker/config.json`, `.netrc`, `.pgpass`, `.pypirc`, `.git-credentials`, and two GCP credential files (`application_default_credentials.json` and `legacy_credentials`) — the `~/.config/gcloud` directory listing is still collected too. It also reads local `.env`, `.env.local`, `.env.production`, `.env.development`, and `secrets.env` files from the working directory, and adds cryptocurrency wallet theft: key files from Solana, Anchor, NEAR, and Sui wallet paths, plus the first three files under `~/.foundry/keystores`. The credential regex gains BEARER, API, INFURA, ALCHEMY, HELIUS, QUICKNODE, ANKR, and PRIVATE_KEY to catch RPC and API provider tokens. Both versions exfiltrate to the same webhook.site endpoint. In 1.0.0, index.js opens with a fake comment claiming it is `@plumenetwork/nest-artifacts`, an unrelated install-time shim — `@plumenetwork/nest-artifacts` is not itself a malicious package, just a leftover label from whatever template the attacker reused across this batch, published by npm account `mssjeep843`. The fake comment was removed in 1.1.0. Five sibling packages from the same account impersonate Euler's EVC, Aerodrome Finance, Camelot AMM, and the BoringVault pattern, sharing this same webhook.site endpoint, byte-identical payload template, and 1.0.0-to-1.1.0 escalation. Two further packages from the same account (PyPI `dlmm` and `dlmm-sdk`, impersonating Meteora's DLMM SDK) ran an equivalent harvester and are tracked separately as MAL-2026-13728 and MAL-2026-13729. Any environment that installed either version should rotate the exposed secrets and treat harvested keys as compromised, prioritizing wallet private keys and RPC/API tokens if 1.1.0 was installed. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (2c46806c21e6a0f5a5593eca11bbd822991f566dc05eb50c7ec56f88b649c3be) Package name typosquats the legitimate @aerodrome-finance scope. Lifecycle hooks auto-execute index.js on npm install, which reads installer secrets from ~/.aws/, ~/.ssh/, ~/.kube/, ~/.docker/, ~/.netrc, ~/.npmrc, ~/.pypirc, ~/.git-credentials, gcloud/solana/anchor/sui key directories, Foundry keystores, and.env files, and scrapes process.env for keys matching KEY|TOKEN|SECRET|PASS|PRIVATE|MNEMONIC|AWS|GITHUB|NPM|WALLET|SEED. The collected data is POSTed to a hardcoded webhook.site endpoint via https.request from a detached child process (spawn(process.execPath, ['-e', src], {detached:true, stdio:'ignore'})) that sleeps 60-240 seconds before sending, to outlive install and scan windows. Sandbox/honeypot evasion is present: host regex checks for scan-/detonation/sandbox/ubuntu-fc-uvm prefixes, non-root/sandbox user checks, canarytoken/honey env checks, and a check for npm mirror registries. Static evidence confirms co-use of child_process, https, os, and fs, with os.hostname() and a POST to https.request in index.js. | GCVE Database | |||
| Critical | 9.1 | EPSS 0.6% | CVE-2026-48039pipeboard-co meta-ads-mcp · Improper Authentication Critical9.1EPSS 0.6%CVE Database V5CVE-2026-48039 Meta Ads MCP is a Model Context Protocol (MCP) server that lets AI assistants run Meta Ads. Prior to version 1.0.109, `AuthInjectionMiddleware.dispatch()` at `http_auth_integration.py:272` unconditionally forwards unauthenticated Streamable HTTP requests to downstream MCP tool handlers without issuing a `401` response, allowing any network-reachable caller to invoke MCP tools without authentication. When no per-request credential is present, tool handlers fall back to the `META_ACCESS_TOKEN` environment variable, and when the downstream Meta Graph API call fails, `api.py:263–269` serialises the raw `httpx` request URL—including the operator's `access_token` as a query parameter—into the JSON-RPC response body, delivering the credential to the unauthenticated caller. Version 1.0.109 fixes the issue. | CVE Database V5 |
Page 17 of 51 · 2 duplicate CVE records merged