CVSS 4.0
2.1 lowCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:PLow (2.1) in rainygao docsys. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:PCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExplain CVE-2026-105157 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105157?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105157?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105157 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| RainyGao DocSys | 2.02.0 |
| RainyGao DocSys | 2.02.1 |
| RainyGao DocSys | 2.02.2 |
| RainyGao DocSys | 2.02.3 |
| RainyGao DocSys | 2.02.4 |
| RainyGao DocSys | 2.02.5 |
| RainyGao DocSys | 2.02.6 |
| RainyGao DocSys | 2.02.7 |
| RainyGao DocSys | 2.02.8 |
| RainyGao DocSys | 2.02.9 |
| RainyGao DocSys | 2.02.10 |
| RainyGao DocSys | 2.02.11 |
| RainyGao DocSys | 2.02.12 |
| RainyGao DocSys | 2.02.13 |
| RainyGao DocSys | 2.02.14 |
| RainyGao DocSys | 2.02.15 |
| RainyGao DocSys | 2.02.16 |
| RainyGao DocSys | 2.02.17 |
| RainyGao DocSys | 2.02.18 |
| RainyGao DocSys | 2.02.19 |
| RainyGao DocSys | 2.02.20 |
| RainyGao DocSys | 2.02.21 |
| RainyGao DocSys | 2.02.22 |
| RainyGao DocSys | 2.02.23 |
| RainyGao DocSys | 2.02.24 |
| RainyGao DocSys | 2.02.25 |
| RainyGao DocSys | 2.02.26 |
| RainyGao DocSys | 2.02.27 |
| RainyGao DocSys | 2.02.28 |
| RainyGao DocSys | 2.02.29 |
| RainyGao DocSys | 2.02.30 |
| RainyGao DocSys | 2.02.31 |
| RainyGao DocSys | 2.02.32 |
| RainyGao DocSys | 2.02.33 |
| RainyGao DocSys | 2.02.34 |
| RainyGao DocSys | 2.02.35 |
| RainyGao DocSys | 2.02.36 |
| RainyGao DocSys | 2.02.37 |
| RainyGao DocSys | 2.02.38 |
| RainyGao DocSys | 2.02.39 |
| RainyGao DocSys | 2.02.40 |
| RainyGao DocSys | 2.02.41 |
| RainyGao DocSys | 2.02.42 |
| RainyGao DocSys | 2.02.43 |
| RainyGao DocSys | 2.02.44 |
| RainyGao DocSys | 2.02.45 |
| RainyGao DocSys | 2.02.46 |
| RainyGao DocSys | 2.02.47 |
| RainyGao DocSys | 2.02.48 |
| RainyGao DocSys | 2.02.49 |
| RainyGao DocSys | 2.02.50 |
| RainyGao DocSys | 2.02.51 |
| RainyGao DocSys | 2.02.52 |
| RainyGao DocSys | 2.02.53 |
| RainyGao DocSys | 2.02.54 |
| RainyGao DocSys | 2.02.55 |
| RainyGao DocSys | 2.02.56 |
| RainyGao DocSys | 2.02.57 |
| RainyGao DocSys | 2.02.58 |
| RainyGao DocSys | 2.02.59 |
| RainyGao DocSys | 2.02.60 |
| RainyGao DocSys | 2.02.61 |
| RainyGao DocSys | 2.02.62 |
| RainyGao DocSys | 2.02.63 |
| RainyGao DocSys | 2.02.64 |
| RainyGao DocSys | 2.02.65 |
| RainyGao DocSys | 2.02.66 |
| RainyGao DocSys | 2.02.67 |
| RainyGao DocSys | 2.02.68 |
| RainyGao DocSys | 2.02.69 |
| RainyGao DocSys | 2.02.70 |
| RainyGao DocSys | 2.02.71 |
| RainyGao DocSys | 2.02.72 |
| RainyGao DocSys | 2.02.73 |
| RainyGao DocSys | 2.02.74 |
| RainyGao DocSys | 2.02.75 |
| RainyGao DocSys | 2.02.76 |
| RainyGao DocSys | 2.02.77 |
| RainyGao DocSys | 2.02.78 |
| RainyGao DocSys | 2.02.79 |
| RainyGao DocSys | 2.02.80 |
| RainyGao DocSys | 2.02.81 |
| RainyGao DocSys | 2.02.82 |
| RainyGao DocSys | 2.02.83 |
| RainyGao DocSys | 2.02.84 |
| RainyGao DocSys | 2.02.85 |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.