Skip to content
vulnerability

CVE-2021-41277

10.0
Critical
KEV · Exploited in wildEPSS 97%Patch available

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.

exploited
Yes, in CISA KEV since 12 Nov 2024fix by 3 Dec 2024 (CISA deadline for US federal agencies)unvetted proof-of-concept code on github
fix
Patch available see the advisory in the references
likelihood
EPSS 97.2%
Published 17 Nov 2021Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

triage
server-sideruntimeWAF can block: yesAV · networkCWE-200· Information ExposureCWE-22· Path Traversal

Can a WAF block it? Yes. Path traversal sends `../` sequences in the request, which WAF rules catch, including the common encodings.

Also consider: response filtering · canonical path validation

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionnonescopechangedconfidentialityhighintegrityhighavailabilitylow
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
common questions

Is CVE-2021-41277 being exploited?

Yes. CVE-2021-41277 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2021-41277?

CVE-2021-41277 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2021-41277?

Yes. A fix has been recorded for CVE-2021-41277. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2021-41277 affect?

CVE-2021-41277 affects metabase:metabase. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
metabase:metabase
affected versions
metabase
  • affected< 0.40.5
  • affected>= 1.0.0 and < 1.40.5

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Unvetted proof-of-concept code on GitHub: 12 GitHub proofs of concept · 1 Nuclei template

Nuclei
GitHub proofs of concept
+8 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
yes
technical impact
total

Assessed by CISA 20 Aug 2025 (SSVC 2.0.3).

timeline

  1. 17 Nov 2021Published
  2. 21 Nov 2021First proof-of-concept repository on GitHub (unvetted) · 3 days later
  3. 12 Nov 2024Added to CISA KEV (exploited in the wild) · 1,087 days (about 3 years) later
  4. 3 Dec 2024CISA remediation due date (US federal agencies) · 21 days later
  5. 20 Aug 2025CISA SSVC assessment: exploitation active · 260 days (about 9 months) later
  6. 7 Oct 2026CVE record last updated · 414 days (about 1 year) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 26 days later

also known as

GHSA-w73v-6p7p-fpfr
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
NVDCVE.orgCVE DetailsSource
3 references in the CVE record: 3 links
  • Linkgithub.com /metabase/metabase/security/advisories/GHSA-w73v-6p7p-fpfr
  • Linkgithub.com /metabase/metabase/commit/042a36e49574c749f944e19cf80360fd3dc322f0
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-41277

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • Nuclei templates: detection templates
  • PoC-in-GitHub: GitHub repositories that claim a proof of concept
  • OSV: advisory aliases and downstream package versions
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved