<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-10T19:47:26.637429+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-2950</id>
    <title>CVE-2026-2950 — lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`</title>
    <updated>2026-10-10T19:47:26.797641+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> lodash, lodash-es, lodash-amd, lodash.unset</p>
<p>Impact:</p>
<p>Lodash versions 4.17.23 and earlier are vulnerable to prototype pollution in the _.unset and _.omit functions. The fix for (CVE-2025-13465: https://github.com/lodash/lodash/security/advisories/GHSA-xxjr-mmjv-4gpg) only guards against string key members, so an attacker can bypass the check by passing array-wrapped path segments. This allows deletion of properties from built-in prototypes such as Object.prototype, Number.prototype, and String.prototype.</p>
<p>The issue permits deletion of prototype properties but does not allow overwriting their original behavior.</p>
<p>Patches:</p>
<p>This issue is patched in 4.18.0.</p>
<p>Workarounds:</p>
<p>None. Upgrade to the patched version.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-2950"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-3v7f-55p6-f55p</id>
    <title>GHSA-3v7f-55p6-f55p — Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching</title>
    <updated>2026-10-10T19:47:26.797742+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: picomatch</p>
<p>### Impact
picomatch is vulnerable to a **method injection vulnerability (CWE-1321)** affecting the `POSIX_REGEX_SOURCE` object. Because the object inherits from `Object.prototype`, specially crafted POSIX bracket expressions (e.g., `[[:constructor:]]`) can reference inherited method names. These methods are implicitly converted to strings and injected into the generated regular expression.</p>
<p>This leads to **incorrect glob matching behavior (integrity impact)**, where patterns may match unintended filenames. The issue does **not enable remote code execution**, but it can cause security-relevant logic errors in applications that rely on glob matching for filtering, validation, or access control.</p>
<p>All users of affected `picomatch` versions that process untrusted or user-controlled glob patterns are potentially impacted.</p>
<p>### Patches</p>
<p>This issue is fixed in picomatch 4.0.4, 3.0.2 and 2.3.2.</p>
<p>Users should upgrade to one of these versions or later, depending on their supported release line.</p>
<p>### Workarounds</p>
<p>If upgrading is not immediately possible, avoid passing untrusted glob patterns to picomatch.</p>
<p>Possible mitigations include:
- Sanitizing or rejecting untrusted glob patterns, especially those containing POSIX character classes like `[[:...:]]`.
- Avoiding the use of POSIX bracket expressions if user input is involved.
- Manually patching the library by modifying `POSIX_REGEX_SOURCE` to use a null prototype:</p>
<p>```js
  const POSIX_REGEX_SOURCE = {
    __proto__: null,
    alnu…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-3v7f-55p6-f55p"/>
  </entry>
</feed>
