CVE-2026-35207 json
deepinid plugin in dde-control-center is configured to skip TLS certificate verification when downloading avatar from remote server
published 7mo ago modified 14d ago also EUVD-2026-20991
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 4%
- public exploits
- 0
- none known
Summary
dde-control-center is the control panel of DDE, the Deepin Desktop Environment. plugin-deepinid is a plugin in dde-control-center, which provides the deepinid cloud service. Prior to 6.1.80, plugin-deepinid is configured to skip TLS certificate verification when fetching the user's avatar from openapi.deepin.com or other providers. An MITM attacker could intercept the traffic, replace the avatar with a malicious or misleading image, and potentially identify the user by the avatar. This vulnerability is fixed in dde-control-center 6.1.80 and 5.9.9.
Patch / fix
Is CVE-2026-35207 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6mo ago
Exploit prediction
0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N |
Affected products
- linuxdeepin dde-control-center
- linuxdeepin deepin-deepinid-plugin
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
- github.com /linuxdeepin/dde-control-center/pull/3146
- github.com /linuxdeepin/dde-control-center/commit/6fc206120be28d9eef7d72258662bcabb834367f
- github.com /linuxdeepin/dde-control-center/commit/cd95b054ff10a35bc9284431631305bd56244b3d
- github.com /linuxdeepin/developer-center/security/advisories/GHSA-jf2h-4vqc-3jgc
Sources
- CVE List CVE-2026-35207
- NVD CVE-2026-35207
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.