<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-14T15:42:54.291841+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/ghsa-mh29-5h37-fv8m</id>
    <title>GHSA-mh29-5h37-fv8m — js-yaml has prototype pollution in merge (&lt;&lt;)</title>
    <updated>2026-10-14T15:42:54.312462+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: js-yaml</p>
<p>### Impact</p>
<p>In js-yaml 4.1.0, 4.0.0, and 3.14.1 and below, it's possible for an attacker to modify the prototype of the result of a parsed yaml document via prototype pollution (`__proto__`). All users who parse untrusted yaml documents may be impacted.</p>
<p>### Patches</p>
<p>Problem is patched in js-yaml 4.1.1 and 3.14.2.</p>
<p>### Workarounds</p>
<p>You can protect against this kind of attack on the server by using `node --disable-proto=delete` or `deno` (in Deno, pollution protection is on by default).</p>
<p>### References</p>
<p>https://cheatsheetseries.owasp.org/cheatsheets/Prototype_Pollution_Prevention_Cheat_Sheet.html</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-mh29-5h37-fv8m"/>
  </entry>
</feed>
