Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

PYSEC-2022-43040

CVE-2022-41381

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI d8s-utility

    Affected
    every version
    Fixed in
    no fixed version recorded

  • PyPI democritus-file-system

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2022-41381: 1.67% estimated exploitation activity in the next 30 days; percentile 76.85 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

The d8s-utility 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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record PYSEC-2022-43040

  2. Revision 1 · created ·

    Published from osv record PYSEC-2022-43031

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-41381

Advisory: PYSEC-2022-43040
IDs: CVE-2022-41381
Record: https://patchnext.com/advisories/cve-2022-41381 (revision 2, source checked 24 Oct 2026, 04:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI d8s-utility: affected every version
- PyPI democritus-file-system: affected every version

## Suggested inspection (read-only)
- `python -m pip show d8s-utility`: prints the installed version. Run with the environment that serves production active.
- `python -m pip show democritus-file-system`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on d8s-utility, democritus-file-system.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/PYSEC-2022-43031 (OSV record PYSEC-2022-43031 lists affected ranges: PyPI d8s-utility >=0)
- Verified: https://osv.dev/vulnerability/PYSEC-2022-43040 (OSV record PYSEC-2022-43040 lists affected ranges: PyPI democritus-file-system >=0)

Commands are suggestions: review each one before running it.

Loading voting…