django-pyas2 through 1.2.3 is vulnerable to OS command injection via the cmd_receive and cmd_send fields on the Partner model. These fields are passed directly to os.system() in pyas2/utils.py without sanitization, allowing an authenticated admin user to execute arbitrary commands on the server when an AS2 message is received or sent.
CVE-2026-42168
Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-17. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(high)
- EG Risk
- 56(Track)EG Risk 56/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity91% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 66%
- KEV
- Not listed
Published
July 17, 2026
Last Modified
July 23, 2026
Advisory Details (3)
Auto-updated Jul 20, 2026vulnerability-research/CVE-2026-42168 at main · m4ty-m/vulnerability-research · GitHub
https://github.com/m4ty-m/vulnerability-research/tree/main/CVE-2026-42168Release v1.2.3 (abhishek-ram/django-pyas2)
Patch available: abhishek-ram/django-pyas2 v1.2.3
https://github.com/abhishek-ram/django-pyas2/releases/tag/v1.2.3GitHub - abhishek-ram/django-pyas2: AS2 file transfer Server built on Python and Django. · GitHub
https://github.com/abhishek-ram/django-pyas2Vendor Advisories for CVE-2026-42168(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 39× in last 7d / 52× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-29 22:57 UTCGHSA enrichment
- 2026-07-29 19:07 UTCGHSA enrichment
- 2026-07-29 15:25 UTCGHSA enrichment
- 2026-07-29 11:42 UTCGHSA enrichment
- 2026-07-29 08:00 UTCGHSA enrichment
- 2026-07-29 04:16 UTCGHSA enrichment
- 2026-07-29 00:34 UTCGHSA enrichment
- 2026-07-28 20:51 UTCGHSA enrichment
- 2026-07-28 17:08 UTCEG score recompute
- 2026-07-28 17:08 UTCGHSA enrichment
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-28 11:52 UTCGHSA enrichment
- 2026-07-28 08:01 UTCGHSA enrichment
- 2026-07-28 04:19 UTCGHSA enrichment
- 2026-07-28 00:37 UTCGHSA enrichment
- 2026-07-27 20:56 UTCGHSA enrichment
- 2026-07-27 17:14 UTCEG score recompute
- 2026-07-27 17:14 UTCGHSA enrichment
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 13:33 UTCGHSA enrichment
- 2026-07-27 09:44 UTCGHSA enrichment
- 2026-07-27 06:03 UTCGHSA enrichment
- 2026-07-27 02:19 UTCGHSA enrichment
- 2026-07-26 22:35 UTCGHSA enrichment
- 2026-07-26 18:52 UTCGHSA enrichment
Show 27 moreShow fewer
- 2026-07-26 15:08 UTCEG score recompute
- 2026-07-26 15:08 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 11:23 UTCEG score recompute
- 2026-07-26 11:23 UTCGHSA enrichment
- 2026-07-26 04:36 UTCEG score recompute
- 2026-07-26 04:36 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:11 UTCEG score recompute
- 2026-07-23 00:23 UTCEG score recompute
- 2026-07-23 00:23 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 18:38 UTCEG score recompute▲ 9.10
- 2026-07-20 18:38 UTCGHSA enrichment
- 2026-07-20 18:37 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:30 UTCEG score recompute
- 2026-07-19 02:30 UTCGHSA enrichment
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-17 22:01 UTCNVD update
- 2026-07-17 19:50 UTCEG score recompute
- 2026-07-17 19:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-78
- CVE-2009-20011EG 10.0CRITICAL
- CVE-2011-10017EG 10.0CRITICAL
- CVE-2012-1166EG 10.0EPSS p91HIGH
- CVE-2012-2976EG 10.0EPSS p92HIGH
- CVE-2012-2953EG 10.0EPSS p99HIGH
- CVE-2011-4502EG 10.0EPSS p92HIGH
- CVE-2011-2148EG 10.0EPSS p92HIGH
- CVE-2011-0382EG 10.0EPSS p90HIGH
- CVE-2011-0381EG 10.0EPSS p92HIGH
- CVE-2011-0372EG 10.0HIGH
Frequently asked(5)
What is CVE-2026-42168?
When was CVE-2026-42168 disclosed?
Is CVE-2026-42168 actively exploited?
What is the CVSS score of CVE-2026-42168?
How do I remediate CVE-2026-42168?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-42168
Is Your Infrastructure Affected by CVE-2026-42168?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.