What is the CVSS score of CVE-2021-41078?

CVE-2021-41078 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 1.5%.

Is there a public PoC exploit available for CVE-2021-41078?

Yes, a public proof-of-concept exploit is available for CVE-2021-41078. Prioritise patching immediately. EPSS: 1.5%.

Is there a patch available for CVE-2021-41078?

Yes, a patch is available for CVE-2021-41078. Update the affected software to the latest version immediately.

Nameko CVE-2021-41078

HIGH

Deserialization of Untrusted Data (CWE-502)

2021-10-26 cve@mitre.org

Deserialization RCE Nameko

7.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.8 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Oct 26, 2021 - 13:15 nvd

HIGH 7.8

DescriptionNVD

Nameko through 2.13.0 can be tricked into performing arbitrary code execution when deserializing the config file.

AnalysisAI

Nameko through 2.13.0 can be tricked into performing arbitrary code execution when deserializing the config file. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as Deserialization of Untrusted Data (CWE-502), which allows attackers to execute arbitrary code through malicious serialized objects. Nameko through 2.13.0 can be tricked into performing arbitrary code execution when deserializing the config file. Affected products include: Nameko. Version information: through 2.13.0.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Avoid deserializing untrusted data. Use safe serialization formats (JSON). Implement integrity checks and type allowlists.