Metabase GeoJSON API Local File Inclusion Vulnerability
metabase — metabase
Metabase is an open source data analytics platform. In affected versions a security issue has been discovered with the custom GeoJSON map (`admin->settings->maps->custom maps->add a map`) support and potential local file inclusion (including environment variables). URLs were not validated prior to being loaded. This issue is fixed in a new maintenance release (0.40.5 and 1.40.5), and any subsequent release after that. If you’re unable to upgrade immediately, you can mitigate this by including rules in your reverse proxy or load balancer or WAF to provide a validation filter before the application.
10.0
97.2%
Vector breakdown
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
- Published
- Nov 17, 2021
- Modified
- Oct 7, 2026
- Added to KEV
- Nov 12, 2024
- Federal patch due
- Dec 3, 2024
CISA required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Weakness classification
Proof-of-concept & exploitation references
Weaponization
Public repositories whose name or description references CVE-2021-41277, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit — cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
No public GitHub repositories referencing CVE-2021-41277 were found at last check. Absence here is not proof no exploit exists — see the references below for vendor advisories and write-ups.
References
Frequently asked questions
What is CVE-2021-41277?
Metabase is an open source data analytics platform. In affected versions a security issue has been discovered with the custom GeoJSON map (`admin->settings->maps->custom maps->add a map`) support and potential local file inclusion (including environment variables). URLs were not validated prior to being loaded. This issue is fixed in a new maintenance release (0.40.5 and 1.40.5), and any subsequent release after that. If you’re unable to upgrade immediately, you can mitigate this by including rules in your reverse proxy or load balancer or WAF to provide a validation filter before the application.
How severe is CVE-2021-41277?
CVE-2021-41277 has a CVSS base score of 10.0 out of 10 (CVSS 3.1).
Is CVE-2021-41277 actively exploited in the wild?
Yes. CVE-2021-41277 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Nov 12, 2024, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2021-41277?
97.2% - meaning FIRST.org's EPSS model estimates a 97.2% probability this vulnerability will be exploited in the wild within 30 days (100% percentile among all scored CVEs).
Is there exploit tooling available for CVE-2021-41277?
Yes - a public Nuclei template referencing CVE-2021-41277 exist in public repositories we checked.
What type of vulnerability is CVE-2021-41277?
CVE-2021-41277 is classified under CWE-200 (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor).
Cross-checked against
Impactr finds and proves whether CVE-2021-41277 — or flaws like it — are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.