<?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-07T13:16:13.151436+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/euvd-2026-329822</id>
    <title>EUVD-2026-329822</title>
    <updated>2026-10-07T13:16:13.219209+00:00</updated>
    <content>EUVD-2026-329822</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-329822"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-47379</id>
    <title>fkie_cve-2026-47379</title>
    <updated>2026-10-07T13:16:13.219288+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, the shared-view password check fell back to strict-equality (===) comparison for legacy plaintext passwords, leaking the password's length and per-character prefix through response timing. This vulnerability is fixed in 2026.05.1.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-47379"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-qhxg-623c-cfjm</id>
    <title>GHSA-qhxg-623c-cfjm — NocoDB: Plaintext Password Comparison in Shared Views</title>
    <updated>2026-10-07T13:16:13.219350+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: nocodb</p>
<p>### Summary
The shared-view password check fell back to strict-equality (`===`) comparison for
legacy plaintext passwords, leaking the password's length and per-character prefix
through response timing.</p>
<p>### Details
The bcrypt branch (hashes starting with `$2a$`/`$2b$`) was unaffected. The legacy
fallback in `View.ts` now uses `crypto.timingSafeEqual` and a same-length dummy
compare on the length-mismatch path, so total comparison time is approximately
length-independent. The EE dashboard model's `verifyPassword` is patched the same way.</p>
<p>### Impact
A network-positioned attacker could mount a timing oracle against shared views whose
passwords predated the bcrypt migration. Exploitation requires the ability to time
shared-view authentication responses but no prior authentication.</p>
<p>### Credit
This issue was reported by [@Proscan-one](https://github.com/Proscan-one).</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-qhxg-623c-cfjm"/>
  </entry>
</feed>
