CVE-2026-36669

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-17. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0

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

An unauthenticated arbitrary file upload vulnerability in ck_upload_handler.php in Feng Office 3.11.13.11 allows remote attackers to upload malicious files (such as .html) to the web-accessible /tmp/ directory.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
75(Attend)
EG Risk 75/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
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

July 17, 2026

Last Modified

July 23, 2026

Advisory Details (2)

Auto-updated Jul 25, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

GitHub - firstlax6t/CVE-2026-36669-FengOffice · GitHub

https://github.com/firstlax6t/CVE-2026-36669-FengOffice
generic

Feng Office: Powerful Project Management Software

https://www.fengoffice.com/

Vendor Advisories for CVE-2026-36669(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 34× in last 7d / 46× 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-28 22:25 UTCGHSA enrichment
  2. 2026-07-28 17:50 UTCEG score recompute
  3. 2026-07-28 17:50 UTCGHSA enrichment
  4. 2026-07-28 13:41 UTCGHSA enrichment
  5. 2026-07-28 09:21 UTCGHSA enrichment
  6. 2026-07-28 05:12 UTCGHSA enrichment
  7. 2026-07-28 01:03 UTCGHSA enrichment
  8. 2026-07-27 20:54 UTCGHSA enrichment
  9. 2026-07-27 16:44 UTCEG score recompute
  10. 2026-07-27 16:44 UTCGHSA enrichment
  11. 2026-07-27 14:13 UTCEPSS rescore
  12. 2026-07-27 12:24 UTCGHSA enrichment
  13. 2026-07-27 08:14 UTCGHSA enrichment
  14. 2026-07-27 04:04 UTCGHSA enrichment
  15. 2026-07-26 23:53 UTCGHSA enrichment
  16. 2026-07-26 19:43 UTCGHSA enrichment
  17. 2026-07-26 15:33 UTCEG score recompute
  18. 2026-07-26 15:33 UTCGHSA enrichment
  19. 2026-07-26 14:54 UTCEPSS rescore
  20. 2026-07-26 14:54 UTCEPSS rescore
  21. 2026-07-26 11:23 UTCEG score recompute
  22. 2026-07-26 11:23 UTCGHSA enrichment
  23. 2026-07-26 04:37 UTCEG score recompute
  24. 2026-07-26 04:36 UTCGHSA enrichment
  25. 2026-07-25 14:18 UTCEPSS rescore
Show 21 more
  1. 2026-07-25 14:18 UTCEPSS rescore
  2. 2026-07-24 14:17 UTCEPSS rescore
  3. 2026-07-24 14:17 UTCEPSS rescore
  4. 2026-07-23 14:18 UTCEPSS rescore
  5. 2026-07-23 14:18 UTCEPSS rescore
  6. 2026-07-23 03:10 UTCEG score recompute
  7. 2026-07-23 00:22 UTCEG score recompute
  8. 2026-07-23 00:22 UTCGHSA enrichment
  9. 2026-07-22 14:08 UTCEPSS rescore
  10. 2026-07-21 15:24 UTCEPSS rescore
  11. 2026-07-20 18:38 UTCEG score recompute▲ 9.80
  12. 2026-07-20 18:38 UTCGHSA enrichment
  13. 2026-07-20 18:37 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-19 14:31 UTCEPSS rescore
  16. 2026-07-19 02:30 UTCEG score recompute
  17. 2026-07-19 02:30 UTCGHSA enrichment
  18. 2026-07-19 02:29 UTCEPSS rescore
  19. 2026-07-17 22:01 UTCNVD update
  20. 2026-07-17 19:50 UTCEG score recompute
  21. 2026-07-17 19:49 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-36669?
CVE-2026-36669 is a critical vulnerability published on July 17, 2026. An unauthenticated arbitrary file upload vulnerability in ckuploadhandler.php in Feng Office 3.11.13.11 allows remote attackers to upload malicious files (such as .html) to the web-accessible /tmp/ directory.
When was CVE-2026-36669 disclosed?
CVE-2026-36669 was first published in the National Vulnerability Database on July 17, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-36669 actively exploited?
CVE-2026-36669 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.5% of all scored CVEs.
What is the CVSS score of CVE-2026-36669?
CVE-2026-36669 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-36669?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-36669, 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-36669

Explore →

Is Your Infrastructure Affected by CVE-2026-36669?

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

Start Free Scan →Browse All CVEs