<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 08 Oct 2026 20:36:37 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-275892</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-275892</link>
      <description>EUVD-2026-275892</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-275892</guid>
    </item>
    <item>
      <title>fkie_cve-2026-31888</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-31888</link>
      <description>&lt;p&gt;Shopware is an open commerce platform. Prior to 6.7.8.1 and 6.6.10.15, the Store API login endpoint (POST /store-api/account/login) returns different error codes depending on whether the submitted email address belongs to a registered customer (CHECKOUT__CUSTOMER_AUTH_BAD_CREDENTIALS) or is unknown (CHECKOUT__CUSTOMER_NOT_FOUND). The &amp;#34;not found&amp;#34; response also echoes the probed email address. This allows an unauthenticated attacker to enumerate valid customer accounts. The storefront login controller correctly unifies both error paths, but the Store API does not — indicating an inconsistent defense. This vulnerability is fixed in 6.7.8.1 and 6.6.10.15.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Shopware is an open commerce platform. Prior to 6.7.8.1 and 6.6.10.15, the Store API login endpoint (POST /store-api/account/login) returns different error codes depending on whether the submitted email address belongs to a registered customer (CHECKOUT__CUSTOMER_AUTH_BAD_CREDENTIALS) or is unknown (CHECKOUT__CUSTOMER_NOT_FOUND). The &amp;#34;not found&amp;#34; response also echoes the probed email address. This allows an unauthenticated attacker to enumerate valid customer accounts. The storefront login controller correctly unifies both error paths, but the Store API does not — indicating an inconsistent defense. This vulnerability is fixed in 6.7.8.1 and 6.6.10.15.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-31888</guid>
    </item>
    <item>
      <title>GHSA-gqc5-xv7m-gcjq — Shopware has user enumeration via distinct error codes on Store API login endpoint</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-gqc5-xv7m-gcjq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: shopware/platform, Packagist: shopware/core&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The Store API login endpoint (`POST /store-api/account/login`) returns different error codes depending on whether the submitted email address belongs to a registered customer (`CHECKOUT__CUSTOMER_AUTH_BAD_CREDENTIALS`) or is unknown (`CHECKOUT__CUSTOMER_NOT_FOUND`). The &amp;#34;not found&amp;#34; response also echoes the probed email address. This allows an unauthenticated attacker to enumerate valid customer accounts. The storefront login controller correctly unifies both error paths, but the Store API does not — indicating an inconsistent defense.&lt;/p&gt;
&lt;p&gt;## CWE&lt;/p&gt;
&lt;p&gt;- **CWE-204**: Observable Response Discrepancy&lt;/p&gt;
&lt;p&gt;## Description&lt;/p&gt;
&lt;p&gt;### Distinct error codes leak account existence&lt;/p&gt;
&lt;p&gt;The login flow in `AccountService::getCustomerByLogin()` calls `getCustomerByEmail()` first, which throws `CustomerNotFoundException` if the email is not found. If the email IS found but the password is wrong, a separate `BadCredentialsException` is thrown:&lt;/p&gt;
&lt;p&gt;```php
// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145
public function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity
{
    if ($this-&amp;gt;isPasswordTooLong($password)) {
        throw CustomerException::badCredentials();
    }&lt;/p&gt;
&lt;p&gt;$customer = $this-&amp;gt;getCustomerByEmail($email, $context);
    // ↑ Throws CustomerNotFoundException with CHECKOUT__CUSTOMER_NOT_FOUND if email unknown&lt;/p&gt;
&lt;p&gt;if ($customer-&amp;gt;hasLegacyPassword()) {
        if (!$this-&amp;gt;legacyPasswordVerifier-&amp;gt;verify($password, $custome…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: shopware/platform, Packagist: shopware/core&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The Store API login endpoint (`POST /store-api/account/login`) returns different error codes depending on whether the submitted email address belongs to a registered customer (`CHECKOUT__CUSTOMER_AUTH_BAD_CREDENTIALS`) or is unknown (`CHECKOUT__CUSTOMER_NOT_FOUND`). The &amp;#34;not found&amp;#34; response also echoes the probed email address. This allows an unauthenticated attacker to enumerate valid customer accounts. The storefront login controller correctly unifies both error paths, but the Store API does not — indicating an inconsistent defense.&lt;/p&gt;
&lt;p&gt;## CWE&lt;/p&gt;
&lt;p&gt;- **CWE-204**: Observable Response Discrepancy&lt;/p&gt;
&lt;p&gt;## Description&lt;/p&gt;
&lt;p&gt;### Distinct error codes leak account existence&lt;/p&gt;
&lt;p&gt;The login flow in `AccountService::getCustomerByLogin()` calls `getCustomerByEmail()` first, which throws `CustomerNotFoundException` if the email is not found. If the email IS found but the password is wrong, a separate `BadCredentialsException` is thrown:&lt;/p&gt;
&lt;p&gt;```php
// src/Core/Checkout/Customer/SalesChannel/AccountService.php:116-145
public function getCustomerByLogin(string $email, string $password, SalesChannelContext $context): CustomerEntity
{
    if ($this-&amp;gt;isPasswordTooLong($password)) {
        throw CustomerException::badCredentials();
    }&lt;/p&gt;
&lt;p&gt;$customer = $this-&amp;gt;getCustomerByEmail($email, $context);
    // ↑ Throws CustomerNotFoundException with CHECKOUT__CUSTOMER_NOT_FOUND if email unknown&lt;/p&gt;
&lt;p&gt;if ($customer-&amp;gt;hasLegacyPassword()) {
        if (!$this-&amp;gt;legacyPasswordVerifier-&amp;gt;verify($password, $custome…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-gqc5-xv7m-gcjq</guid>
    </item>
  </channel>
</rss>
