How severe is CVE-2021-46361?

CVE-2021-46361 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-46361?

CVE-2021-46361 affects the following packages: info.magnolia:magnolia-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2021-46361?

Update info.magnolia:magnolia-core to 6.2.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-46361 is resolved across your whole dependency graph.

How do I detect CVE-2021-46361 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for info.magnolia:magnolia-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-46361 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2021-46361 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2021-46361, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2021-46361?

CVE-2021-46361 has an EPSS (Exploit Prediction Scoring System) score of 2.8%, placing it in the 86th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2021-46361 published, and has it been updated?

CVE-2021-46361 was published on February 12, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

CVE-2021-46361 — magnolia-core

CRITICAL

CVE-2021-46361 is a critical-severity (CVSS 9.8) remote code execution vulnerability in info.magnolia:magnolia-core. 1 public exploit reference exists, so weaponization risk is real. A fix is available for info.magnolia:magnolia-core — see the affected versions and patch details below.

Arbitrary code execution in Magnolia CMS

Published

Feb 12, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-46361 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕info.magnolia:magnolia-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

An issue in the Freemark Filter of Magnolia CMS v6.2.11 and below allows attackers to bypass security restrictions and execute arbitrary code via a crafted FreeMarker payload.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`info.magnolia:magnolia-core`	all versions	6.2.12`info.magnolia:magnolia-core:6.2.12`

Affected Products

1 product · 1 configurations

Application

magnolia cmsmagnolia-cms

< 6.2.12

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An issue in the Freemark Filter of Magnolia CMS v6.2.11 and below allows…

github.comNVDFeb 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for info.magnolia:magnolia-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update info.magnolia:magnolia-core to 6.2.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-46361 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

An issue in the Freemark Filter of Magnolia CMS v6.2.11 and below allows attackers to bypass security restrictions and execute arbitrary code via a crafted FreeMarker payload.

O3 Security · Impact-Aware SCA

Is CVE-2021-46361 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works