VulnerabilityPublished 12 Mar 2026

CVE-2026-32100: swag platform-security · Information Exposure

Affects swag platform-securitySource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium · fixed in 4.0.7 : update swag platform-security when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.0.7, 3.0.12, 2.0.16

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade platform-security to 4.0.7, 3.0.12 or 2.0.16; shopware/platform-security to 3.0.12 or 2.0.16.

Affected software

Product	Affected	Fixed in
swagplatform-security	Affected >=4.0.0 <4.0.7	Fixed in 4.0.7
swagplatform-security	Affected >=3.0.0 <3.0.12	Fixed in 3.0.12
swagplatform-security	Affected <2.0.16	Fixed in 2.0.16
GitHubshopware/platform-security`pkg:github/shopware/platform-security`Other threats	Affected <2.0.16 >=3.0.0 <3.0.12	Fixed in 2.0.16 3.0.12

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-32100, organizations should promptly upgrade affected Shopware installations to versions 2.0.16, 3.0.12, 4.0.7, or later, where the vulnerability has been addressed. If immediate upgrading is not feasible, restrict access to the /api/_info/config endpoint by implementing network-level controls such as firewall rules, IP whitelisting, or VPN access to limit exposure to trusted users only. Additionally, consider implementing API gateway policies or web application firewall (WAF) rules to block or monitor requests to this endpoint. Review and minimize the amount of sensitive information exposed via public APIs, following the principle of least privilege and information disclosure. Regularly audit API endpoints for unintended data exposure and apply security hardening best practices. Monitoring logs for unusual access patterns to this endpoint can help detect reconnaissance attempts. Finally, maintain an up-to-date inventory of Shopware versions deployed across the organization to ensure timely patch management and vulnerability remediation.

Description

CVE-2026-32100 is a medium severity vulnerability in the Shopware open commerce platform's swag platform-security component. The /api/_info/config API endpoint exposes sensitive information about active security fixes without requiring authentication. This information disclosure could aid attackers in identifying unpatched vulnerabilities. The issue affects versions prior to 2.0.16, 3.0.12, and 4.0.7 and has a CVSS score of 5.

Impact

The primary impact of CVE-2026-32100 is the unauthorized disclosure of sensitive information related to active security fixes in Shopware installations. This leakage can enable attackers to better understand the security state of a target system, potentially allowing them to identify unpatched vulnerabilities or misconfigurations. While the vulnerability does not directly compromise system integrity or availability, it increases the risk of subsequent targeted attacks such as exploitation of known but unpatched vulnerabilities. Organizations using affected versions of Shopware may face increased reconnaissance by attackers, which could lead to more sophisticated and successful intrusion attempts. The exposure of security fix details can also undermine the confidentiality of internal security practices and timelines. Although no active exploits are reported, the ease of access (no authentication or user interaction required) means that opportunistic attackers or automated scanners could leverage this information. This risk is particularly relevant for e-commerce platforms handling sensitive customer and payment data, where any compromise could have significant financial and reputational consequences.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/shopware/shopware/security/advisories/GHSA-64rg-pgjv-4v33 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Mar 2026, 02:31 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats