dcnnt-py is vulnerable to command injection via Notification Handler

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

EPSS

• CVE-2023-1000: 1.32% estimated exploitation activity in the next 30 days; percentile 70.92 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A vulnerability was found in cyanomiko dcnnt-py up to 0.9.0. It has been classified as critical. Affected is the function main of the file dcnnt/plugins/notifications.py of the component Notification Handler. The manipulation leads to command injection. It is possible to launch the attack remotely. Upgrading to version 0.9.1 is able to address this issue. The patch is identified as b4021d784a97e25151a5353aa763a741e9a148f5. It is recommended to upgrade the affected component. VDB-262230 is the identifier assigned to this vulnerability.

Published by the source

27 Apr 2024, 09:30 UTC

Last modified by the source

7 Jul 2026, 17:56 UTC

Source last checked

26 Oct 2026, 13:13 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-8p42-7597-p2f6

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-8p42-7597-p2f6

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

# Patch Next advisory brief: CVE-2023-1000

Advisory: dcnnt-py is vulnerable to command injection via Notification Handler
IDs: CVE-2023-1000, GHSA-8p42-7597-p2f6
Record: https://patchnext.com/advisories/cve-2023-1000 (revision 2, source checked 26 Oct 2026, 13:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: dcnnt 0.9.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI dcnnt: affected <= 0.9.0; fixed in 0.9.1

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on dcnnt.
- 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/GHSA-8p42-7597-p2f6 (OSV record GHSA-8p42-7597-p2f6 lists affected ranges: PyPI dcnnt >=0 <0.9.1 (fixed))
- Verified: https://github.com/advisories/GHSA-8p42-7597-p2f6 (GitHub-reviewed advisory GHSA-8p42-7597-p2f6 lists affected ranges: PyPI dcnnt >=0 <=0.9.0)

Commands are suggestions: review each one before running it.