<?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-11-18T10:25:56.738352+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/cleanstart-2026-on76952</id>
    <title>CLEANSTART-2026-ON76952 — Security fix for GHSA-xw5c-jc7x-gf75 applied in: druid-fips 34.0.0-r2, druid-fips 35.0.1-r2, druid-fips 36.0.0-r1, drui…</title>
    <updated>2026-11-18T10:25:56.740299+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: druid-fips</p>
<p>Security vulnerability affects the druid-fips package. This issue is resolved in later releases. See references for vulnerability details.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cleanstart-2026-on76952"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-40458</id>
    <title>CVE-2026-40458 — Cross-Site Request Forgery in PAC4J</title>
    <updated>2026-11-18T10:25:56.740384+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PAC4J</p>
<p>PAC4J is vulnerable to Cross-Site Request Forgery (CSRF). A malicious attacker can craft a specially designed website which, when visited by a user, will automatically submit a forged cross-site request with a token whose hash collides with the victim's legitimate CSRF token. Importantly, the attacker does not need to know the victim’s CSRF token or its hash prior to the attack. Collisions in the deterministic String.hashCode() function can be computed directly, reducing the effective token's security space to 32 bits. This bypasses CSRF protection, allowing profile updates, password changes, account linking, and any other state-changing operations to be performed without the victim's consent.</p>
<p>This issue was fixed in PAC4J versions 5.7.10 and 6.4.1</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-40458"/>
  </entry>
</feed>
