CVE Intelligence
CISA KEV High

CVE-2022-36537 — ZK Framework AuUploader Unspecified Vulnerability

ZK Framework v9.6.1, 9.6.0.1, 9.5.1.3, 9.0.1.2 and 8.6.4.1 allows attackers to access sensitive information via a crafted POST request sent to the component AuUploader.

Published Aug 26, 2022 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: mitre

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

CISA KEV · Feb 27, 2023 R used by ransomware (CISA) Detection templates (Nuclei) · 1Proofs of concept on GitHub · 3
How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Used in ransomware campaigns (CISA)+10
  • Public exploit/PoC (nuclei, github)+10
  • EPSS 95.4% (30-day exploitation probability)+15
  • Technical severity (high)+6
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Feb 27, 2023
EPSS FIRST
95.4%
ahead of 100% of scored CVEs · Oct 14, 2026
Affects
Zkoss
Zk Framework and 1 more
CVSS base
7.5
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — tracker.zkoss.org (NIST National Vulnerability Database)
  • Maven Org.zkoss.zk:zk: fixed in version 8.6.4.2 — github.com (GitHub Security Advisories)
  • Maven Org.zkoss.zk:zk: fixed in version 9.0.1.3 — github.com (GitHub Security Advisories)
  • Maven Org.zkoss.zk:zk: fixed in version 9.5.1.4 — github.com (GitHub Security Advisories)
  • Maven Org.zkoss.zk:zk: fixed in version 9.6.0.2 — github.com (GitHub Security Advisories)
  • Maven Org.zkoss.zk:zk: fixed in version 9.6.2 — github.com (GitHub Security Advisories)

CISA required action CISA

Apply updates per vendor instructions.

US federal deadline: Mar 20, 2023 — passed 1305 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Zkoss Zk Framework, Maven Org.zkoss.zk:zk).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. Apply the fixed version or the patch documented under Remediation.
  5. EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
  6. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Zkoss Zk Framework < 8.6.4.2≥ 9.0.0 and < 9.0.1.3≥ 9.5.0 and < 9.5.1.3≥ 9.6.0 and < 9.6.2 Vulnerable NIST National Vulnerability Database
Maven Org.zkoss.zk:zk < 8.6.4.2≥ 9.0.0.0 and < 9.0.1.3≥ 9.5.0.0 and < 9.5.1.4≥ 9.6.0.0 and < 9.6.0.2≥ 9.6.1 and < 9.6.2 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.5 CVSS 3.1 High 3.9 3.6 nvd@nist.gov via NIST National Vulnerability Database
7.5 CVSS 3.1 High 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
7.5 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.5 CVSS 3.1 High — — CISA-ADP via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov)

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Feb 27, 2023
Federal deadline
Mar 20, 2023
passed 1305 day(s) ago
Ransomware use
Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Detection templates (Nuclei)
Proofs of concept on GitHub

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 95.40%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Hunt retroactively in logs from before Feb 27, 2023 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 13, 2026 · GitHub Security Advisories
  • Affected products added · maven/org.zkoss.zk:zk
    Oct 13, 2026 · GitHub Security Advisories
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · zkoss/zk framework
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2023
  • Added to CISA KEV catalog
    Feb 26, 2023 · CISA
  • 2022
  • CVE published
    Aug 26, 2022 · mitre

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

7 on the record

Elsewhere on this site

Zkoss
every CVE for this vendor
2023-02
what else CISA listed that month

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2022-36537 is "ZK Framework AuUploader Unspecified Vulnerability", rated High. It affects Zk Framework (Zkoss); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.5 describes technical severity. EPSS 95.40% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.