CVE-2024-45815: @backstage/plugin-catalog-backend Prototype Pollution vulnerability
Impact A malicious actor with authenticated access to a Backstage instance with the catalog backend plugin installed is able to interrupt the service using a specially crafted query to the catalog API. Patches This has been fixed in the 1.26.0 release of the @backstage/plugin-catalog-backend package.
Published Sep 17, 2024 · Updated Nov 18, 2024
Affected packages
@backstage/plugin-catalog-backend
- Ecosystem
- npm
- Affected
- < 1.26.0
- Fixed in
- 1.26.0
- Check
npm ls @backstage/plugin-catalog-backend
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
A malicious actor with authenticated access to a Backstage instance with the catalog backend plugin installed is able to interrupt the service using a specially crafted query to the catalog API.
Patches
This has been fixed in the 1.26.0 release of the @backstage/plugin-catalog-backend package.
References
If you have any questions or comments about this advisory:
Open an issue in the Backstage repository Visit our Discord, linked to in Backstage README
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-115923
Backstage catalog rules can be bypassed for URL locations using encoded path segments
medium6.5Oct 28, 2026CVE-2026-106496
Backstage: Inconsistent enforcement of allowed location types during catalog processing
low3.1Oct 7, 2026CVE-2026-106498
Backstage: Improper URL validation in catalog entity placeholder resolution
high7.7Oct 7, 2026
