漏洞（CVE）
Common Vulnerabilities and Exposures
漏洞列表
全部 CVE
CISA - 已被利用漏洞
OWASP - 漏洞
按类别统计 CVE
按厂商搜索
按产品搜索
按年份排序
CVE 2026
CVE 2025
CVE 统计
按年份/月份统计 CVE
按类别统计 CVE
按 OWASP 统计 CVE
按 CVSS 评分统计 CVE
漏洞最多的 100 大厂商
漏洞最多的 100 大产品
专项视图
CVE 严重评分
CVE EPSS > 70%
CVE 高危评分
CVE 网络（向量）
CVE 本地（向量）
CVE 物理（向量）
CVE
CVE（Common Vulnerabilities and Exposures）是一份公开披露的计算机安全缺陷列表。
OWASP
OWASP Top 10 是一项识别并记录 Web 应用程序十大安全漏洞的倡议。
CISA KEV
CISA 已知被利用漏洞（KEV）是一项识别并公布已知被利用漏洞列表的倡议。
厂商与产品（CPE）
厂商与产品
厂商列表
所有厂商
漏洞最多的 100 大厂商
产品列表
所有产品
漏洞最多的 100 大产品
CPE（Common Platform Enumeration）是一种用于命名硬件、软件和操作系统的标准化方案。CPE 提供了一种结构化命名方案，可根据厂商、产品名称、版本、更新、版次和语言等属性唯一标识和分类信息技术系统、平台和软件包。
弱点（CWE）
Common Weakness Enumeration
CWE 列表
全部 CWE
CWE 视图
CWE 类别
专项视图
CWE Top 25 (2023)
CWE Top 25 (2022)
CWE Top 25 (2021)
软件开发
硬件设计
研究概念
最新 5 条 CWE
CWE-1463
(2026-10-28 00:00 +00:00)
CWE-1462
(2026-10-28 00:00 +00:00)
CWE-1466
(2026-10-28 00:00 +00:00)
CWE-1465
(2026-10-28 00:00 +00:00)
CWE-1464
(2026-10-28 00:00 +00:00)
CWE（Common Weakness Enumeration）是软件弱点和漏洞的综合列表与分类。它作为描述架构、设计、代码或实现中可能导致漏洞的软件安全弱点的通用语言。
攻击模式（CAPEC）
Common Attack Pattern Enumeration and Classification
CAPEC 列表
全部 CAPEC
CAPEC 视图
CAPEC 类别
专项视图
攻击机制
攻击领域
WASC 威胁分类 2.0
ATT&CK 相关攻击模式
OWASP 相关攻击模式
最新 5 条 CAPEC
CAPEC-701
(2023-01-24 00:00 +00:00)
CAPEC-700
(2023-01-24 00:00 +00:00)
CAPEC-702
(2023-01-24 00:00 +00:00)
CAPEC-699
(2023-01-24 00:00 +00:00)
CAPEC-691
(2022-09-29 00:00 +00:00)
CAPEC（Common Attack Pattern Enumeration and Classification）是一个全面的公开资源，记录了网络攻击中对手常用的攻击模式。该知识库旨在理解和阐明常见漏洞及攻击者利用它们的方法。
服务与价格
价格与授权
创建账户
帮助与信息
常见问题与帮助
博客与文章
数据库合作伙伴
联系我们
搜索：CVE ID、CWE ID、CAPEC ID、厂商或 CVE 关键词
最近搜索：
未找到结果
请尝试其他关键词
简体中文
English
Français
Deutsch
Español
Italiano
Português
Nederlands
Polski
日本語
简体中文
繁體中文
한국어
Bahasa Indonesia
Tiếng Việt
浅色
深色
系统
CVE Find - 提醒系统
随时保持了解
创建免费账户
开设免费账户
登录账户
管理您的提醒
CVE-2026-113650：详情
首页
Common Vulnerabilities and Exposures (CVE)
CVE-2026-113650：详情
CVE-2026-113650
评分 / 严重程度
5.3
/
中危
发布日期
2026-10-20
17h17
+00:00
向量
Network
修改日期
2026-10-28
14h16
+00:00
官方链接
CVE.org
NVD
指定 CVE 通知
随时了解指定 CVE 的变更。
管理通知
自定义提醒
激活您的个性化提醒！
要激活提醒，只需登录您的
免费账户
。如果尚未登录，请选择以下其中一个选项。
登录账户
创建免费账户
指定 CVE 通知
随时了解指定 CVE 的变更。
发送提醒的触发条件：与上次发送内容对比，CISA、EPSS、CVSS、CWE、解决方案或 CPE 发生差异。
参数
您可以设置标题，该标题将出现在发送的提醒中。
在此输入 CVE ID，格式如 CVE-2025-1234
发送计划
发送频率
需要更高级的方案
每小时
即时响应新发布内容
需要更高级的方案
每天
在选定日期发送邮件
需要更高级的方案
每周
在选定日期发送摘要
每月
每月汇总
小时
每小时
每 15 分钟 (需要更高级的方案)
每 30 分钟 (需要更高级的方案)
分钟
00
05
10
15
20
25
30
35
40
45
50
55
适用日期
星期一
星期二
星期三
星期四
星期五
星期六
星期日
执行时间 (UTC)
适用日期
星期一
星期二
星期三
星期四
星期五
星期六
星期日
执行时间 (UTC)
月份
每月
选定月份
一月
二月
三月
四月
五月
六月
七月
八月
九月
十月
十一月
十二月
日期
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
执行时间 (UTC)
*
必填字段
every
1
2
3
4
5
6
7
8
9
10
11
12
every
lastday
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
every
1
2
3
4
5
6
7
every
every4
every12
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
every15
every30
0
5
10
15
20
25
30
35
40
45
50
55
创建日期
-
上次执行
-
下次执行
-
CVE 描述
ApostropheCMS is an open-source Node.js content management system. In sanitize-html 2.18.0, when an
is not allowed and disallowedTagsMode is 'discard' (the defaults), its raw-text content is re-sanitized by a recursive call to sanitizeHtml(text, options). The recursion has no bound and starts each nested call with a fresh state. This vulnerability is fixed in 2.18.1. </div> </div> <div class="card card-flush py-4"> <div class="card-header"> <div class="card-title"> <h2>CVE 信息</h2> </div> </div> <div class="card-body pt-0"> <h2 class="tw-h3">相关弱点</h2> <div class="table-responsive"> <table class="table table-striped gy-7 gs-7"> <thead> <tr class="fw-semibold fs-6 text-gray-800 border-bottom border-gray-200"> <th><nobr>CWE-ID</nobr></th> <th>弱点名称</th> <th>来源</th> </tr> </thead> <tbody> <tr> <td><nobr><a href="/zh-hans/cwe/cwe-674.html">CWE-674</a></nobr></td> <td><b>Uncontrolled Recursion</b><br>The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.</td> <td></td> </tr> </tbody> </table> </div> <div class="separator my-10"></div> <h3>指标</h3> <div class="table-responsive"> <table class="table table-striped gy-7 gs-7"> <thead> <tr class="fw-semibold fs-6 text-gray-800 border-bottom border-gray-200"> <th>指标</th> <th>评分</th> <th>严重程度</th> <th>CVSS 向量</th> <th>来源</th> </tr> </thead> <tbody> <tr> <td>V3.1</td> <td>5.3</td> <td>MEDIUM</td> <td> CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L <div class="m-0"> <div class="d-flex align-items-center collapsible toggle mb-0 collapsed" data-bs-toggle="collapse" data-bs-target="#metric-179440968132636" aria-expanded="false"> <div class="btn btn-sm btn-icon mw-20px btn-active-color-primary me-5"> <i class="ki-duotone ki-minus-square toggle-on text-primary fs-4"> <span class="path1"></span> <span class="path2"></span> </i> <i class="ki-duotone ki-plus-square toggle-off fs-4"> <span class="path1"></span> <span class="path2"></span> <span class="path3"></span> </i> </div> <span class="text-gray-700 cursor-pointer mb-0">更多信息</span> </div> <div id="metric-179440968132636" class="fs-7 ms-1 collapse" style=""> <div class="mb-4"> <div class="d-flex align-items-center ps-10 mb-n1"> <div class="text-gray-600 fs-7"> <h4 class='bg-light border border-gray-300 rounded p-2'>Base: Exploitabilty Metrics</h4><p>The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.</p><div class='tw-h5' style='padding-left:10px'>Attack Vector</div><p style='padding-left:10px'>This metric reflects the context by which vulnerability exploitation is possible.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>Network</p></div><div style='flex: 1;margin-left:5px;'><p>The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).</p></div></div><div class='tw-h5' style='padding-left:10px'>Attack Complexity</div><p style='padding-left:10px'>This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.</p></div></div><div class='tw-h5' style='padding-left:10px'>Privileges Required</div><p style='padding-left:10px'>This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>None</p></div><div style='flex: 1;margin-left:5px;'><p>The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.</p></div></div><div class='tw-h5' style='padding-left:10px'>User Interaction</div><p style='padding-left:10px'>This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>None</p></div><div style='flex: 1;margin-left:5px;'><p>The vulnerable system can be exploited without interaction from any user.</p></div></div><h4 class='bg-light border border-gray-300 rounded p-2'>Base: Scope Metrics</h4><p>The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.</p><div class='tw-h5' style='padding-left:10px'>Scope</div><p style='padding-left:10px'>Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>Unchanged</p></div><div style='flex: 1;margin-left:5px;'><p>An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.</p></div></div><h4 class='bg-light border border-gray-300 rounded p-2'>Base: Impact Metrics</h4><p>The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.</p><div class='tw-h5' style='padding-left:10px'>Confidentiality Impact</div><p style='padding-left:10px'>This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>None</p></div><div style='flex: 1;margin-left:5px;'><p>There is no loss of confidentiality within the impacted component.</p></div></div><div class='tw-h5' style='padding-left:10px'>Integrity Impact</div><p style='padding-left:10px'>This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>None</p></div><div style='flex: 1;margin-left:5px;'><p>There is no loss of integrity within the impacted component.</p></div></div><div class='tw-h5' style='padding-left:10px'>Availability Impact</div><p style='padding-left:10px'>This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.</p></div></div><h4 class='bg-light border border-gray-300 rounded p-2'>Temporal Metrics</h4><p>The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.</p><h4 class='bg-light border border-gray-300 rounded p-2'>Environmental Metrics</h4><p>These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.</p> </div> </div> </div> </div> </div> </td> <td>security-advisories@github.com</td> </tr> </tbody> </table> </div> <div class="separator my-10"></div> <h2 class='tw-h3'>参考资料</h2><div style='margin-bottom: 10px;'><a href='https://github.com/apostrophecms/apostrophe/commit/06e4b377f3c360f9e89c32dccd7e505ad5ddf498' target='_blank'>https://github.com/apostrophecms/apostrophe/commit/06e4b377f3c360f9e89c32dccd7e505ad5ddf498 <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br></div><div style='margin-bottom: 10px;'><a href='https://github.com/apostrophecms/apostrophe/commit/40b989b1a9dd23d30029b8ce7668634265cfe5ea' target='_blank'>https://github.com/apostrophecms/apostrophe/commit/40b989b1a9dd23d30029b8ce7668634265cfe5ea <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br></div><div style='margin-bottom: 10px;'><a href='https://github.com/apostrophecms/apostrophe/releases/tag/sanitize-html@2.18.1' target='_blank'>https://github.com/apostrophecms/apostrophe/releases/tag/sanitize-html@2.18.1 <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br></div><div style='margin-bottom: 10px;'><a href='https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-c9rx-x947-fp3h' target='_blank'>https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-c9rx-x947-fp3h <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br></div><div style='margin-bottom: 10px;'><a href='https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-c9rx-x947-fp3h' target='_blank'>https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-c9rx-x947-fp3h <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br></div><div class="separator my-10"></div> </div> </div> </div> </div> </div> </div> <!--end::Container--> <!--begin::Footer--> <div class="footer py-4 d-flex flex-lg-column" id="kt_footer"> <div class="container-xxl d-flex flex-column flex-md-row align-items-center justify-content-between"> <div class="text-gray-900 order-2 order-md-1"> <span class="text-muted fw-semibold me-1">2026©</span> <a href="https://www.tesweb.com" target="_blank" class="text-gray-800 text-hover-primary">tesweb SA</a>, <a href="https://www.bexxo.ch" target="_blank" class="text-gray-800 text-hover-primary">bexxo Cyber Security</a> </div> <ul class="menu menu-gray-600 menu-hover-primary fw-semibold order-1"> <li class="menu-item"> <a href="/zh-hans/official.html" class="menu-link px-2">数据来源</a> </li> <li class="menu-item"> <a href="/zh-hans/gdpr.html" class="menu-link px-2">GDPR</a> </li> <li class="menu-item"> <a href="#" id="gdpr-manage-cookies" class="menu-link px-2">管理 Cookie</a> </li> <li class="menu-item"> <a href="/zh-hans/contact.html" class="menu-link px-2">联系</a> </li> <li class="menu-item"> <a href="/zh-hans/plan-price.html" class="menu-link px-2">购买</a> </li> <li class="menu-item"> <a href="https://www.linkedin.com/company/cve-find/" class="menu-link px-2" target="_blank"><img src="/media/social/linkedin.svg" width="40" height="40" alt="LinkedIn Account"/></a> </li> <li class="menu-item"> <a href="https://www.facebook.com/people/CVE-Find-Alert/61561116452093/" class="menu-link px-2" target="_blank"><img src="/media/social/facebook.svg" width="40" height="40" alt="Facebook Account"/></a> </li> <li class="menu-item"> <a href="https://x.com/cvefindcom" class="menu-link px-2" target="_blank"><img src="/media/social/twitter.svg" width="40" height="40" alt="Twitter Account"/></a> </li> </ul> </div> </div> <div class="footer py-4"> <div class="container-xxl align-items-center justify-content-between"> cvefind.com 上展示的信息来源于多个精心选择的权威数据源。CVE 数据由 <a href="https://cve.mitre.org/" target="_blank">MITRE Corporation</a> 和 <a href="https://nvd.nist.gov/" target="_blank">National Vulnerability Database (NVD)</a> 提供。已知被利用漏洞（KEV）目录来源于 <a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog" target="_blank">Cybersecurity and Infrastructure Security Agency (CISA)</a>，EPSS 评分来自 <a href="https://www.first.org/epss/" target="_blank">FIRST.org</a>。此外，软件弱点（CWE）和常见攻击模式（CAPEC）数据由 <a href="https://mitre.org/" target="_blank">MITRE Corporation</a> 维护，硬件和软件配置（CPE）信息由 <a href="https://nvd.nist.gov/products/cpe" target="_blank">NVD</a> 提供。 </div> </div> </div> </div> </div> <!--begin::Javascript--> <script>var hostUrl = "assets/";</script> <script src="/plugins/global/plugins.bundle.min.1743008562.js"></script> <script src="/js/scripts.bundle.1718974735.js"></script> <script src="/js/app/custom.min.1788264851.js"></script> <script src="/js/app/base.zh-hans.min.1793721675.js" defer></script> <script src="/plugins/custom/datatables/datatables.bundle.1718974031.js"></script> <script src="/js/aceeditor/ace.1715679271.js"></script> <script src="/js/app/bloc/cve/epss.min.1738322185.js"></script> <script src="/js/app/bloc/cve/exploitdb.min.1738322201.js"></script> <script src="/js/app/account/manageAlertNeedAccount.min.1782998772.js" defer></script> <div class="ea-slot d-lg-none" data-ea-anchor="mobile" data-ea-pub="cvefindcom" data-ea-type="text" data-ea-style="fixedfooter" data-ea-kw="security|cybersecurity|vulnerability|cve"></div> <style> /* Encart EthicalAds centré dans son emplacement */ .ea-slot [data-ea-publisher]{margin-left:auto;margin-right:auto;} /* Format horizontal : remplit la largeur de la colonne (variable officielle EthicalAds) */ .ea-slot [data-ea-publisher].horizontal{--ea-image-placement-width-horizontal:100%;} </style> <script async src="https://media.ethicalads.io/media/client/ethicalads.min.js"></script> <script src="/js/app/ads/ethicalads.min.1792667231.js" defer></script> </body> </html> <script> var cookieTimezoneBrowser = function () { let timeZone = Intl.DateTimeFormat().resolvedOptions().timeZone; var offset = -new Date().getTimezoneOffset(); var prefix = offset >= 0 ? '+' : '-'; var timezoneOffset = prefix + Math.floor(Math.abs(offset) / 60).toString().padStart(2, '0') + ':' + (Math.abs(offset) % 60).toString().padStart(2, '0'); document.cookie = "tw-browser=" + timeZone+"|"+ timezoneOffset+ "; path=/"; } cookieTimezoneBrowser(); </script>
