Unrated

Embedded Malicious Code in ctx

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 ctx
Affected
>= 0.1.2.post1
Fixed in
no fixed version recorded

Sources

GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-67r3-h899-9w95 lists affected ranges: PyPI ctx >=0.1.2.post1
VerifiedObserved 26 Oct 2026, 13:08 UTCStructured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

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.

The ctx hosted project on PyPI was taken over via user account compromise and replaced with a malicious project which contained runtime code which collected the content of os.environ.items() when instantiating Ctx objects.

Dates and revisions

Published by the source: 2 Jun 2022, 15:46 UTC
Last modified by the source: 11 Jan 2023, 05:07 UTC
Source last checked: 26 Oct 2026, 13:08 UTC

Revision 1 · created · 26 Oct 2026
Published from ghsa record GHSA-67r3-h899-9w95

Agent brief

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

# Patch Next advisory brief: GHSA-67r3-h899-9w95

Advisory: Embedded Malicious Code in ctx
IDs: GHSA-67r3-h899-9w95
Record: https://patchnext.com/advisories/ghsa-67r3-h899-9w95 (revision 1, source checked 26 Oct 2026, 13:08 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 ctx: affected >= 0.1.2.post1

## Suggested inspection (read-only)
- `python -m pip show ctx`: 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 ctx.
- 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://github.com/advisories/GHSA-67r3-h899-9w95 (GitHub-reviewed advisory GHSA-67r3-h899-9w95 lists affected ranges: PyPI ctx >=0.1.2.post1)

Commands are suggestions: review each one before running it.

Loading voting…