How severe is CVE-2021-46364?

CVE-2021-46364 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-46364?

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

How do I fix CVE-2021-46364?

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

How do I detect CVE-2021-46364 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-46364 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

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

Yes. There are 1 known exploit references for CVE-2021-46364, 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-46364?

CVE-2021-46364 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 75th 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.

What type of vulnerability is CVE-2021-46364?

CVE-2021-46364 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2021-46364 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

HIGH severity

CVE-2021-46364 — magnolia-core

HIGH

CVE-2021-46364 is a high-severity (CVSS 7.8) Deserialization of Untrusted Data 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.

Deserialization of Untrusted Data 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 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk

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

How urgent is this, really

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

Where this sits among everything scored

Of 385,738 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

A vulnerability in the Snake YAML parser of Magnolia CMS v6.2.3 and below allows attackers to execute arbitrary code via a crafted YAML file.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

magnolia cmsmagnolia-cms

< 6.2.4

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.

A vulnerability in the Snake YAML parser of Magnolia CMS v6.2.3 and belo…

github.comNVDMar 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.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-46364 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

A vulnerability in the Snake YAML parser of Magnolia CMS v6.2.3 and below allows attackers to execute arbitrary code via a crafted YAML file.

O3 Security · Impact-Aware SCA

Is CVE-2021-46364 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.8/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CWE Classification

CWE-502Deserialization of Untrusted Data

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Feb 12, 2022

First exploit

Mar 29, 2022

Last updated

Nov 8, 2023

Identifiers

CVE-2021-46364

References

Advisorynvd.nist.gov Webdocs.magnolia-cms.com Webgithub.com

Related vulnerabilities

Also affects magnolia-core

This CVE is high severity; 4 of 4 other CVEs affecting magnolia-core are rated as high or higher (top: critical).

CVE-2021-46365CVE-2021-46363CVE-2021-46366CVE-2021-46361

Same weakness: CWE-502

This CVE is high severity; 3 of 4 other CVEs with CWE-502 are rated as high or higher (top: critical).

CVE-2025-66455CVE-2025-59953CVE-2026-49400CVE-2026-50646Browse all CWE-502

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedNov 8, 2023

CVE-2021-46364 — magnolia-core

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2021-46364 in your dependencies?