<?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-21T08:48:29.252006+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-188884</id>
    <title>EUVD-2026-188884</title>
    <updated>2026-10-21T08:48:29.255102+00:00</updated>
    <content>EUVD-2026-188884</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-188884"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2023-41336</id>
    <title>fkie_cve-2023-41336</title>
    <updated>2026-10-21T08:48:29.255146+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>ux-autocomplete is a JavaScript Autocomplete functionality for Symfony. Under certain circumstances, an attacker could successfully submit an entity id for an `EntityType` that is *not* part of the valid choices. The problem has been fixed in `symfony/ux-autocomplete` version 2.11.2.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2023-41336"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-4cpv-669c-r79x</id>
    <title>GHSA-4cpv-669c-r79x — Prevent injection of invalid entity ids for "autocomplete" fields</title>
    <updated>2026-10-21T08:48:29.255201+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: symfony/ux-autocomplete</p>
<p>### Impact
Under certain circumstances, an attacker could successfully submit an entity id for an `EntityType` that is *not* part of the valid choices.</p>
<p>Affected applications are any that use:</p>
<p>* A custom `query_builder` option to limit the valid results;
AND
* An `EntityType` with `'autocomplete' =&gt; true` or a custom [AsEntityAutocompleteField](https://symfony.com/bundles/ux-autocomplete/current/index.html#usage-in-a-form-with-ajax).</p>
<p>Under this circumstance, if an id is submitted, it is accepted even if the matching record would not be returned by the custom query built with `query_builder`.</p>
<p>### Patches</p>
<p>The problem has been fixed in `symfony/ux-autocomplete` version 2.11.2.</p>
<p>### Workarounds
Upgrade to version 2.11.2 or greater of `symfony/ux-autocomplete` or perform extra validation after submit to verify the selected option is valid.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-4cpv-669c-r79x"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2023-41336</id>
    <title>gsd-2023-41336</title>
    <updated>2026-10-21T08:48:29.255304+00:00</updated>
    <content>gsd-2023-41336</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2023-41336"/>
  </entry>
</feed>
