Security readout for executives and security teams
Plain-English summary
Metabase custom GeoJSON maps loaded URLs without proper validation. In affected versions, an unauthenticated network attacker could potentially expose local server files, including environment variables. That can reveal secrets and undermine data platform trust. Metabase fixed the issue in 0.40.5, 1.40.5, and later releases.
Executive priority
Treat this as urgent for any reachable Metabase instance. KEV status and critical scoring mean remediation should be tracked as a priority security action, especially where Metabase can access sensitive analytics data or secrets.
Technical view
CVE-2021-41277 affects Metabase custom maps under admin settings. URL validation was missing before GeoJSON resources were loaded, creating local file inclusion and information disclosure risk. The CVSS 3.1 score is 10.0 with network, unauthenticated exploitation characteristics. The CVE lists CWE-200 and CWE-22.
Likely exposure
Organizations running Metabase versions before 0.40.5, or Enterprise 1.x versions from 1.0.0 before 1.40.5, should assume exposure if instances are reachable over a network.
Exploitation context
CISA KEV inclusion supports known exploitation. The provided sources do not include exploit mechanics, prevalence, or affected deployment patterns beyond the Metabase version ranges and custom GeoJSON map feature.
Researcher notes
The core issue is missing URL validation in custom GeoJSON map loading, with potential local file inclusion and environment variable disclosure. Evidence supports affected versions and fixed releases, but the provided bundle does not document exploit details or indicators of compromise.
Mitigation direction
- Upgrade Metabase to 0.40.5, 1.40.5, or any later release.
- If upgrade is delayed, add reverse proxy, load balancer, or WAF URL validation filters.
- Restrict administrative settings access to trusted users and networks.
- Review Metabase guidance before applying any compensating control.
- Prioritize exposed internet-facing Metabase instances first.
Validation and detection
- Inventory all Metabase instances and record exact versions.
- Flag versions below 0.40.5 and 1.x versions below 1.40.5.
- Check whether custom GeoJSON maps are configured in admin map settings.
- Review logs for custom map changes and unexpected file or environment access indicators.
- Confirm remediation by verifying the upgraded version.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-41277 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L3.96Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/metabase/metabase/security/advisories/GHSA-w73v-6p7p-fpfrCVE reference · x_refsource_CONFIRM
- https://github.com/metabase/metabase/commit/042a36e49574c749f944e19cf80360fd3dc322f0CVE reference · x_refsource_MISC
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-41277CVE reference · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.