A security vulnerability has been detected in guohongze adminset up to 0.61. Affected by this vulnerability is an unknown functionality of the file delivery/deli.py of the component Delivery Deployment Endpoint. The manipulation of the argument project_id leads to authorization bypass. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-16217
Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-07-19. a secondary CVSS source baseline 6.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 44(Track)EG Risk 44/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 computedSeverity63% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 12.6%
- KEV
- Not listed
Published
July 19, 2026
Last Modified
July 20, 2026
Advisory Details (2)
Auto-updated Jul 19, 2026Delivery deployment endpoint lacks project-level authorization · Issue #161 · guohongze/adminset · GitHub
https://github.com/guohongze/adminset/issues/161GitHub - guohongze/adminset: 自动化运维平台:CMDB、CD、DevOps、资产管理、任务编排、持续交付、系统监控、运维管理、配置管理 · GitHub
https://github.com/guohongze/adminset/Vendor Advisories for CVE-2026-16217(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 17× 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-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 23:56 UTCEG score recompute
- 2026-07-22 23:55 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 20:41 UTCNVD updateCVSS v4 → 2.1
- 2026-07-20 19:12 UTCMITRE cvelistV5CVSS v4 → 5.3
- 2026-07-20 17:49 UTCEG score recompute
- 2026-07-20 17:49 UTCGHSA enrichment
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 06:24 UTCEG score recompute
- 2026-07-19 06:23 UTCNVD updateCVSS v4 → 2.1
- 2026-07-19 05:53 UTCEG score recompute
- 2026-07-19 05:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639 · CWE-285
Frequently asked(5)
What is CVE-2026-16217?
When was CVE-2026-16217 disclosed?
Is CVE-2026-16217 actively exploited?
What is the CVSS score of CVE-2026-16217?
How do I remediate CVE-2026-16217?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16217
Is Your Infrastructure Affected by CVE-2026-16217?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.