<?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-02T09:04:20.651299+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/bit-neo4j-2026-1337</id>
    <title>BIT-neo4j-2026-1337 — Insufficient escaping of unicode characters in query log</title>
    <updated>2026-10-02T09:04:20.654017+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: neo4j</p>
<p>Insufficient escaping of unicode characters in query log in Neo4j Enterprise and Community editions prior to 2026.01 can lead to XSS if the user opens the logs in a tool that treats them as HTML. There is no security impact on Neo4j products, but this advisory is released as a precaution to treat the logs as plain text if using versions prior to 2026.01.</p>
<p>Proof of concept exploit:  https://github.com/JoakimBulow/CVE-2026-1337</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-neo4j-2026-1337"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-267525</id>
    <title>EUVD-2026-267525</title>
    <updated>2026-10-02T09:04:20.654066+00:00</updated>
    <content>EUVD-2026-267525</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-267525"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-1337</id>
    <title>fkie_cve-2026-1337</title>
    <updated>2026-10-02T09:04:20.654083+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>Insufficient escaping of unicode characters in query log in Neo4j Enterprise and Community editions prior to 2026.01 can lead to XSS if the user opens the logs in a tool that treats them as HTML. There is no security impact on Neo4j products, but this advisory is released as a precaution to treat the logs as plain text if using versions prior to 2026.01.</p>
<p>Proof of concept exploit:  https://github.com/JoakimBulow/CVE-2026-1337</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-1337"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-xr72-g735-4vwp</id>
    <title>GHSA-xr72-g735-4vwp — Neo4j Enterprise and Community editions have insufficient escaping of unicode characters in query log</title>
    <updated>2026-10-02T09:04:20.654108+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: org.neo4j:neo4j</p>
<p>Insufficient escaping of unicode characters in query log in Neo4j Enterprise and Community editions prior to 2026.01 can lead to XSS if the user opens the logs in a tool that treats them as HTML. There is no security impact on Neo4j products, but this advisory is released as a precaution to treat the logs as plain text if using versions prior to 2026.01.</p>
<p>Proof of concept exploit:  https://github.com/JoakimBulow/CVE-2026-1337</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-xr72-g735-4vwp"/>
  </entry>
</feed>
