Skip to content
Fencer Intel
high 7.8

CVE-2021-41078 json

Nameko Arbitrary code execution due to YAML deserialization

published 5y ago modified 4mo ago also GHSA-6p52-jr3q-c94g , PYSEC-2021-383 , EUVD-2021-0138

cvss
7.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 75%
public exploits
0
none known

Summary

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

Patch / fix

  • pypi nameko 2.14.0, 3.0.0rc10

Is CVE-2021-41078 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.54% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/nameko/nameko/security/advisories/GHSA-6p52-jr3q-c94g referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.1 8.6 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi nameko
<2.14.0
>=3.0.0rc0, <3.0.0rc10
2.14.0
3.0.0rc10

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.