Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Malicious code in changes-lxc-wrapper (PyPI)

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 changes-lxc-wrapper

    Affected
    <= 0.0.0>= 0.1.0, <= 0.1.0
    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
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

--- _-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (23181d1a705554588eb6fb03e8cee4af7e0c815e74d8b40d7bd13a39944ccae9) The distribution `changes-lxc-wrapper` ships a trivial package whose top-level import name is `ca_certificates`, creating a mismatch between the distribution name and the import namespace it occupies. The shipped `init.py` only defines a `version` constant and an `info()` function returning a placeholder string. There are no install or build hooks, no top-level import-time side effects, no subprocess or network activity, and no credential or filesystem access. Package metadata is placeholder (`Your Name` / `you@example.com`). No installer-side harmful behavior is present in the shipped code; the only concern is namespace shadowing on the common `ca_certificates` import name.

Source: kam193 (6db4cc796d2ddd54fcbb0a46270cff980f711a93a5fff30675499291d9bc41f8) Installing the package or importing the module exfiltrates basic…

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

    Amended from osv record MAL-2026-18326

  2. Revision 1 · created ·

    Published from osv record MAL-2026-18326

Agent brief

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

# Patch Next advisory brief: mal-2026-18326

Advisory: Malicious code in changes-lxc-wrapper (PyPI)
IDs: mal-2026-18326
Record: https://patchnext.com/advisories/mal-2026-18326 (revision 2, source checked 30 Oct 2026, 06:40 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 changes-lxc-wrapper: affected <= 0.0.0; >= 0.1.0, <= 0.1.0

## Suggested inspection (read-only)
- `python -m pip show changes-lxc-wrapper`: 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 changes-lxc-wrapper.
- 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/MAL-2026-18326 (OSV record MAL-2026-18326 lists affected ranges: PyPI changes-lxc-wrapper >=0.0.0 =0.1.0 <=0.1.0)

Commands are suggestions: review each one before running it.

Loading voting…