CVE Intelligence
High

CVE-2026-116016 — yudao-cloud through 2026.09 Data Permission Bypass via data-permission-enable Header

yudao-cloud through 2026.09 contains an authorization bypass vulnerability that allows authenticated users to evade row-level data scope restrictions by sending a data-permission-enable header set to false. Attackers can add this header to /admin-api requests, which DataPermissionRpcWebFilter trusts, to read or modify other departments' and users' records within the same tenant.

Published Oct 24, 2026 · Updated Oct 26, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: VulnCheck

Who exploits it and how urgent it is

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

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3
  • Technical severity (high)+6

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
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.25%
ahead of 17% of scored CVEs · Oct 27, 2026
Affects
YunaiV
Yudao-cloud
CVSS base
7.1
High · 3 source(s)

Remediation

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

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

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 (YunaiV Yudao-cloud).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
YunaiV Yudao-cloud ≤ 2026.09 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

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

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
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.1 CVSS 4.0 High — — disclosure@vulncheck.com via NIST National Vulnerability Database
7.1 CVSS 4.0 High — — VulnCheck via CVE Program (cve.org) e CISA ADP
7.1 CVSS 3.1 High 2.8 4.2 disclosure@vulncheck.com via NIST National Vulnerability Database
7.1 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.1 CVSS 3.1 High — — VulnCheck via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-807

Other CVEs with this weakness →

EPSS over time FIRST

Oct 25, 2026 → Oct 27, 2026 · 3 reading(s) · max 0.25%

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).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Received → Deferred
    Oct 26, 2026 · NIST National Vulnerability Database
  • Affected products added · yunaiv/yudao-cloud
    Oct 24, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 24, 2026
  • CVSS changed · 7.1
    Oct 24, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 24, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 24, 2026 · Alertas do Telegram
  • CVE published
    Oct 24, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

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

References

8 on the record

Elsewhere on this site

YunaiV
every CVE for this vendor
CWE-807
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-116015 yudao-cloud through 2026.09 IDOR via after-sale-log list endpoint 4d
  • CVE-2026-58448 yudao-cloud < 2026.06 - BPM Module Broken Access Control via process-instance API Jun 30, 2026
  • CVE-2026-9464 YunaiV yudao-cloud Admin API Endpoint create IotDataSinkHttpConfig server-side request forgery May 25, 2026
  • CVE-2026-7710 YunaiV yudao-cloud Ruoyi-Vue-Pro JwtAuthenticationTokenFilter.java doFilterInternal improper authentication May 3, 2026
  • CVE-2026-7678 YunaiV yudao-cloud GoViewDataServiceImpl.java getDataBySQL sql injection May 3, 2026
  • CVE-2026-7679 YunaiV yudao-cloud OAuth2TokenServiceImpl.java getAccessToken improper authentication May 3, 2026

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 fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • 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-2026-116016 is "yudao-cloud through 2026.09 Data Permission Bypass via data-permission-enable Header", rated High. It affects Yudao-cloud (YunaiV); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.1 describes technical severity. EPSS 0.25% 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.