Skip to main content
No exploitation reported

CVE-2022-41380

No exploitation reported by the sources we read.

  • Published2022-10-11
  • WeaknessCWE-434

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

The d8s-yaml package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. The backdoor is the democritus-file-system package. The affected version is 0.1.0.

Timeline

dates in UTC
  1. 2022-10-1122:15CVE publishedNVD

Versions per branch

OSV · NVD
d8s-yaml
BranchAffectedFixed in
—all versionsno fix published
Democritus d8s-yaml
BranchAffectedFixed in
0.1= 0.1.0no fix published
democritus-file-system
BranchAffectedFixed in
—all versionsno fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2022-10-11
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-rm8m-wpg7-4976

Frequently asked questions

What is CVE-2022-41380?

The d8s-yaml package for Python, as distributed on PyPI, included a potential code-execution backdoor inserted by a third party. The backdoor is the democritus-file-system package. The affected version is 0.1.0.

Is CVE-2022-41380 actively exploited?

Active exploitation of CVE-2022-41380 has not been confirmed. Its EPSS score was 1.7% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-41380?

CVE-2022-41380 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running d8s-yaml? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record