CVE-2021-41277: Metabase GeoJSON API Local File Inclusion
Metabase · listed in the CISA catalog of actively exploited vulnerabilities since 2024-11-12.
- CVSS v3.1 (CVE record)
- 10.0
- critical
- EPSS (exploit probability, 30 days)
- 97%
- higher than 99.8% of all CVEs
- Added to CISA KEV
- 2024-11-12
- US federal due date 2024-12-03
- Automatable (CISA SSVC)
- yes
- technical impact: total
CVE-2021-41277 explained
CVE-2021-41277 is a local file inclusion flaw in the custom GeoJSON map support of Metabase, an open source data analytics platform. URLs were not validated before being loaded, which can expose local files, including environment variables. CISA lists it as known to be exploited, so unpatched Metabase servers are at serious risk.
Impact
A remote attacker without credentials or user interaction can read local files on the Metabase server, including environment variables, over the network. These may hold secrets such as credentials. The scope is changed, with high confidentiality and integrity impact. CISA rates it automatable with total technical impact, so it can be exploited at scale. CISA lists it as known to be exploited. Ransomware use is unknown.
Who is affected
The CVE record lists metabase versions < 0.40.5 and versions ≥ 1.0.0, < 1.40.5 as affected. The structured fixedIn field in the CVE record names no fixed version. The vulnerability description states that the issue is fixed in maintenance releases 0.40.5 and 1.40.5 and any subsequent release.
Written with AI from the data on this page and checked against it automatically.
Official description
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.
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- metabaseAffectedFixed in
- < 0.40.5
- ≥ 1.0.0
- < 1.40.5
not stated
| Product | Affected | Fixed in |
|---|---|---|
| metabase |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: github.com/metabase/metabase/security/advisories/GHSA-w73…
- CISA's deadline for US federal agencies: 2024-12-03 (passed) – a useful benchmark for everyone else, too.
What to do
- Upgrade Metabase to
0.40.5or1.40.5or any later release, as stated in the vulnerability description. - If you cannot upgrade immediately, add validation rules in your reverse proxy, load balancer or WAF in front of Metabase, per the vendor's guidance.
- Restrict network access to Metabase so it is not exposed to the internet unnecessarily.
- Check servers for signs of compromise and rotate secrets stored in environment variables or files readable by Metabase.
- Follow the vendor advisory and CISA's required action: apply mitigations or discontinue use if mitigations are unavailable.
The structured CVE data names no fixed version, but the description states the fix is in 0.40.5 and 1.40.5 and later. Until you can upgrade, follow CISA's required action: apply the vendor's mitigations, such as validation filters in a reverse proxy, load balancer or WAF, or discontinue use if mitigations are unavailable. Check the vendor advisory for details.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Questions about CVE-2021-41277
- Is CVE-2021-41277 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-11-12, with a US federal due date of 2024-12-03. Whether it is used in ransomware campaigns is unknown.
- Which versions fix the issue?
- According to the description, maintenance releases
0.40.5and1.40.5and any subsequent release fix it. The structured fixed-version field of the CVE record is empty. - What can I do if I cannot upgrade right away?
- The vendor suggests adding rules in your reverse proxy, load balancer or WAF to provide a validation filter before requests reach Metabase. Also limit network exposure and plan the upgrade promptly.
Written with AI from the data on this page and checked against it automatically.
References
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.