CVE-2026-32100
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedShopware is an open commerce platform. /api/_info/config route exposes information about active security fixes. This vulnerability is fixed in 2.0.16, 3.0.12, and 4.0.7.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe /api/_info/config endpoint in Shopware exposes information about active security fixes applied to the system. This information disclosure allows attackers to determine which security patches are present and potentially identify remaining unpatched vulnerabilities.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Shopware installationIdentify if Shopware commerce platform is running in the environment by checking for Shopware-specific files, processes, or web application fingerprintsAffected if Shopware is installed and running in the environment
-
Check endpoint accessibilitySend an HTTP GET request to the /api/_info/config endpoint on the Shopware server (e.g., https://example.com/api/_info/config)Affected if The endpoint returns an HTTP 200 response instead of 404 or 403
-
Inspect response contentExamine the JSON or text response from the endpoint to see if it contains information about applied security patches, fixes, or vulnerability statusAffected if The response contains details about security fixes, patch levels, or vulnerability status of the system
-
Verify information sensitivityDetermine if the exposed information could help an attacker identify which specific vulnerabilities remain unpatched by comparing the disclosed fixes against known CVE listsAffected if The endpoint reveals specific security fixes that could be cross-referenced with known CVEs to identify remaining vulnerabilities
A user is affected if the /api/_info/config endpoint is publicly accessible and returns information about applied security patches or fixes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Shopware to version 2.0.16, 3.0.12, or 4.0.7 (depending on the major branch in use) to remove the vulnerable endpoint or disable the /api/_info/config route.
Shopware 2.0.16, 3.0.12, or 4.0.7 (depending on your current major version line)
- Identify the currently installed Shopware version by checking the installation or consulting version documentation
- Upgrade to Shopware 2.0.16 (if on 2.x line), 3.0.12 (if on 3.x line), or 4.0.7 (if on 4.x line)
- After upgrading, verify that the /api/_info/config route no longer exposes information about active security fixes
- Confirm the upgrade was successful by checking the Shopware admin panel or version endpoint
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32100 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32100 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data