CVE-2026-16016

HIGHPre-NVD 7.37.3—
EchelonGraph scoreHIGH confidence

Score 7.3 from GitHub Security Advisory published 2026-07-17. a secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
7.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A vulnerability was identified in poco-ai poco-claw up to 0.5.4. This issue affects the function run_task of the file executor/app/api/v1/task.py. The manipulation of the argument callback_url leads to server-side request forgery. The attack is possible to be carried out remotely. The exploit is publicly available and might be used. The reported GitHub issue was closed automatically due to inactivity.

CVSS v3
7.3
EG Score
7.3(high)
EG Risk
64(Attend)
EG Risk 64/100SSVC: Attend

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 computed
Severity73% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
20.9%
KEV
Not listed

Published

July 17, 2026

Last Modified

July 17, 2026

Advisory Details (2)

Auto-updated Jul 17, 2026
No patch confirmed yet.
generic

[Security] Unauthenticated `callback_url` SSRF in Poco executor allows attacker-directed outbound requests and callback data disclosure · Issue #138 · poco-ai/poco-claw · GitHub

https://github.com/poco-ai/poco-claw/issues/138
generic

GitHub - poco-ai/poco-claw: A more beautiful and easier-to-use alternative to OpenClaw. It features a nicer Web UI, built-in IM support, a sandboxed runtime and channel-based team collaboration. Under the hood, it is powered by a Claude Code–based agent. · GitHub

https://github.com/poco-ai/poco-claw/

Vendor Advisories for CVE-2026-16016(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 8× in last 7d / 15× 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.

  1. 2026-07-24 14:17 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:05 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:24 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:30 UTCEPSS rescore
  8. 2026-07-19 02:28 UTCEPSS rescore
  9. 2026-07-17 18:37 UTCEG score recompute
  10. 2026-07-17 18:37 UTCGHSA enrichment
  11. 2026-07-17 16:00 UTCNVD updateCVSS v4 → 5.5
  12. 2026-07-17 15:34 UTCEG score recompute
  13. 2026-07-17 15:34 UTCGHSA enrichment
  14. 2026-07-17 14:10 UTCEG score recompute
  15. 2026-07-17 14:09 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16016?
CVE-2026-16016 is a high vulnerability published on July 17, 2026. A vulnerability was identified in poco-ai poco-claw up to 0.5.4. This issue affects the function runtask of the file executor/app/api/v1/task.py. The manipulation of the argument callbackurl leads to server-side request forgery. The attack is possible to be carried out remotely. The exploit is…
When was CVE-2026-16016 disclosed?
CVE-2026-16016 was first published in the National Vulnerability Database on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16016 actively exploited?
CVE-2026-16016 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-16016?
CVE-2026-16016 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-16016?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16016, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-16016

Explore →

Is Your Infrastructure Affected by CVE-2026-16016?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs