#1 · PT-2025-40791 · Oracle · Bi Publisher
Inkmoro
+3
·
Published
2025-10-04
·
Updated
2025-10-15
·
CVE-2025-61882
10
Critical
Base
AV:N/AC:L/Au:N/C:C/I:C/A:C
Exploit
Fix
RCE
XXE
HTTP Request/Response Smuggling
SSRF
Improper Authentication
Improper Access Control
Path traversal
Related posts · 484
2025-10-15 10:27:23
-
📝 In multiple locations, there is a possible way to access data displayed on the screen due to side channel information disclosure. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
-
📅 Published: 04/09/2025
-
📈 CVSS: 5.5
-
🧭 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
-
📣 Mentions: 2
-
⚠️ Priority: 4
-
📝 Analysis: A side channel information disclosure vulnerability exists in multiple locations, potentially allowing local data exposure without requiring additional execution privileges or user interaction. No known exploits have been detected in the wild. Given the low Exploitability Score (EPSS) and CVSS score of 5.5, this is classified as a priority 4 issue, indicating a low risk at this time.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A BitLocker security bypass vulnerability has been identified, enabling remote attackers to compromise sensitive data with moderate exploitability and high impact. While no in-the-wild activity has been confirmed yet, it is a priority 2 issue due to its high CVSS score.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A Windows BitLocker Security Feature Bypass vulnerability has been identified (CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C). Currently, no known exploits are active in the wild. Given the high CVSS score and pending analysis, it's crucial to assess potential impact on affected systems.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A Windows BitLocker Security Feature Bypass vulnerability has been identified. This issue allows unauthorized access with potential data compromise. No known exploits have been detected in the wild, but due to its high impact and moderate exploitability, it is a priority 2 vulnerability requiring attention.
-
📝 Sudo before 1.9.17p1 allows local users to obtain root access because /etc/nsswitch.conf from a user-controlled directory is used with the --chroot option.
-
📅 Published: 30/06/2025
-
📈 CVSS: 9.3
-
🛡️ CISA KEV: True
-
🧭 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
-
📣 Mentions: 75
-
⚠️ Priority: 1+
-
📝 Analysis: A local privilege escalation vulnerability exists in Sudo before 1.9.17p1, enabling local users to gain root access due to improper handling of user-controlled directories with the --chroot option. Currently, no known exploits are active in the wild, making this a priority 4 issue according to our scoring system. Please update affected systems to the latest version.
-
📝 No description available.
-
📅 Published: 05/10/2025
-
📈 CVSS: 9.8
-
🛡️ CISA KEV: True
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📣 Mentions: 38
-
⚠️ Priority: 1+
-
📝 Analysis: A critical (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) vulnerability has been identified, with no description available. As of now, no known in-the-wild activity has been reported (CISA KEV). Due to its high severity and currently low exploitability, it is classified as a priority 2 vulnerability.
-
📝 n/a
-
📈 CVSS: 9.8
-
🧭 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📝 Analysis: Debian Linux - 7zip
-
📝 n/a
-
📈 CVSS: 9.8
-
🧭 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📝 Analysis: Debian Linux - 7zip
-
📝 No description available.
-
📅 Published: 12/10/2025
-
📈 CVSS: 7.5
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
-
📣 Mentions: 13
-
⚠️ Priority: 2
-
📝 Analysis: A remote code execution vulnerability in version-unspecified software module allows attackers to execute commands; currently no exploits detected in the wild, making it a priority 2 issue due to high CVSS score but low Exploitability Scoring System (ESS) score.
-
📝 In the Linux kernel, the following vulnerability has been resolved: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice Savino says: We are writing to report that this recent patch (141d34391abbb315d68556b7c67ad97885407547) [1] can be bypassed, and a UAF can still occur when HFSC is utilized with NETEM. The patch only checks the cl->cl_nactive field to determine whether it is the first insertion or not [2], but this field is only incremented by init_vf [3]. By using HFSC_RSC (which uses init_ed) [4], it is possible to bypass the check and insert the class twice in the eltree. Under normal conditions, this would lead to an infinite loop in hfsc_dequeue for the reasons we already explained in this report [5]. However, if TBF is added as root qdisc and it is configured with a very low rate, it can be utilized to prevent packets from being dequeued. This behavior can be exploited to perform subsequent insertions in the HFSC eltree and cause a UAF. To fix both the UAF and the infinite loop, with netem as an hfsc child, check explicitly in hfsc_enqueue whether the class is already in the eltree whenever the HFSC_RSC flag is set. [1] https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=141d34391abbb315d68556b7c67ad97885407547 [2] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L1572 [3] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L677 [4] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L1574 [5] https://lore.kernel.org/netdev/8DuRWwfqjoRDLDmBMlIfbrsZg9Gx50DHJc1ilxsEBNe2D6NMoigR_eIRIG0LOjMc3r10nUUZtArXx4oZBIdUfZQrwjcQhdinnMis_0G7VEk=@willsroot.io/T/#u
-
📅 Published: 06/06/2025
-
📈 CVSS: 0
-
🧭 Vector: n/a
-
📣 Mentions: 12
-
⚠️ Priority: 4
-
📝 Analysis: A UAF vulnerability has been identified in Linux kernel's net_sched when utilizing HFSC with NETEM. The patch (141d3439) can be bypassed, causing a UAF under specific conditions involving TBF and low rates. To mitigate, explicitly check for class presence during hfsc_enqueue if the HFSC_RSC flag is set. Currently, this vulnerability has low exploitability and activity in the wild (CISA KEV: Priority 4).
2025-10-15 10:05:41
2025-10-15 04:40:07
#2 · PT-2025-28847 · Fortinet · Fortiweb
0Xbigshaq
·
Published
2025-07-08
·
Updated
2025-10-14
·
CVE-2025-25257
10
Critical
Base
AV:N/AC:L/Au:N/C:C/I:C/A:C
Exploit
Fix
RCE
SQL injection
Related posts · 268
2025-10-14 16:15:22
2025-10-12 16:44:23
- 📝 7zip
- 📈 CVSS: 9.8
- 🧭 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- ⚠️ Priority: 1
- 📝 Analysis: Pending NVD publication
- 📝 7zip
- 📈 CVSS: 9.8
- 🧭 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- ⚠️ Priority: 1
- 📝 Analysis: Pending NVD publication
- 📝 An improper neutralization of special elements used in an SQL command ('SQL Injection') vulnerability [CWE-89] in Fortinet FortiWeb version 7.6.0 through 7.6.3, 7.4.0 through 7.4.7, 7.2.0 through 7.2.10 and below 7.0.10 allows an unauthenticated attacker to execute unauthorized SQL code or commands via crafted HTTP or HTTPs requests.
- 📈 CVSS: 9.8
- 🛡️ CISA KEV: True
- 🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- ⚠️ Priority: 1+
- 📝 Analysis: Confirmed Exploitation in the Wild
-
📝 Microsoft SharePoint Server Remote Code Execution Vulnerability
-
📅 Published: 20/07/2025
-
📈 CVSS: 9.8
-
🛡️ CISA KEV: True
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:W/RC:C
-
📣 Mentions: 13
-
⚠️ Priority: 1+
-
📝 Analysis: A critical Remote Code Execution vulnerability has been identified in Microsoft SharePoint Server, with high impact and exploitability through network access. No known in-the-wild activity reported, but priority is 4 due to low EPSS and CVSS scores. Verify against versions mentioned in the description.
-
📝 Incomplete authorization of linked device synchronization messages in WhatsApp for iOS prior to v2.25.21.73, WhatsApp Business for iOS v2.25.21.78, and WhatsApp for Mac v2.25.21.78 could have allowed an unrelated user to trigger processing of content from an arbitrary URL on a targets device. We assess that this vulnerability, in combination with an OS-level vulnerability on Apple platforms (CVE-2025-43300), may have been exploited in a sophisticated attack against specific targeted users.
-
📅 Published: 29/08/2025
-
📈 CVSS: 8
-
🛡️ CISA KEV: True
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
-
📣 Mentions: 12
-
⚠️ Priority: 1+
-
📝 Analysis: Unauthorized linked device synchronization messages in WhatsApp for iOS prior v2.25.21.73, WhatsApp Business for iOS v2.25.21.78, and WhatsApp for Mac v2.25.21.78 may have been exploited in targeted attacks, leveraging CVE-2025-43300 on Apple platforms. This is a priority 2 vulnerability due to high CVSS score and potential for sophistication, despite no confirmed exploits detected.
-
📝 Due to a deserialization vulnerability in SAP NetWeaver, an unauthenticated attacker could exploit the system through the RMI-P4 module by submitting malicious payload to an open port. The deserialization of such untrusted Java objects could lead to arbitrary OS command execution, posing a high impact to the applications confidentiality, integrity, and availability.
-
📅 Published: 09/09/2025
-
📈 CVSS: 10
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
-
📣 Mentions: 28
-
⚠️ Priority: 2
-
📝 Analysis: Unauthenticated attacker can exploit SAP NetWeaver via deserialization in RMI-P4 module, leading to arbitrary OS command execution, posing a high impact on confidentiality, integrity, and availability. No confirmed exploits detected; prioritize due to high CVSS score and low EPSS.
-
📝 No description available.
-
📅 Published: 05/10/2025
-
📈 CVSS: 9.8
-
🛡️ CISA KEV: True
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📣 Mentions: 38
-
⚠️ Priority: 1+
-
📝 Analysis: A critical (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) vulnerability has been identified, with no description available. As of now, no known in-the-wild activity has been reported (CISA KEV). Due to its high severity and currently low exploitability, it is classified as a priority 2 vulnerability.
-
📝 The Service Finder Bookings plugin for WordPress is vulnerable to privilege escalation via authentication bypass in all versions up to, and including, 6.0. This is due to the plugin not properly validating a users cookie value prior to logging them in through the service_finder_switch_back() function. This makes it possible for unauthenticated attackers to login as any user including admins.
-
📅 Published: 01/08/2025
-
📈 CVSS: 9.8
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📣 Mentions: 14
-
⚠️ Priority: 2
-
📝 Analysis: Unauthenticated attackers can escalate privileges in Service Finder Bookings for WordPress (up to version 6.0). This is due to insufficient cookie validation during login through service_finder_switch_back(). No known exploits have been detected, but the high CVSS score and potential impact on administrative permissions make this a priority 2 vulnerability. Verify versions before taking action.
-
📝 In Progress Telerik UI for AJAX, versions 2011.2.712 to 2025.1.218, an unsafe reflection vulnerability exists that may lead to an unhandled exception resulting in a crash of the hosting process and denial of service.
-
📅 Published: 14/05/2025
-
📈 CVSS: 7.5
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
-
📣 Mentions: 8
-
⚠️ Priority: 2
-
📝 Analysis: Unsafe reflection vulnerability discovered in In Progress® Telerik® UI for AJAX versions 2011.2.712 to 2025.1.218 can lead to a hosting process crash, causing denial of service. No known exploits detected; prioritize accordingly as a level 2 vulnerability due to high CVSS score and currently low exploit potential.
-
📝 In the default installation and configuration of Gladinet CentreStack and TrioFox, there is an unauthenticated Local File Inclusion Flaw that allows unintended disclosure of system files. Exploitation of this vulnerability has been observed in the wild. This issue impacts Gladinet CentreStack and Triofox: All versions prior to and including16.7.10368.56560
-
📅 Published: 09/10/2025
-
📈 CVSS: 6.2
-
🧭 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
-
📣 Mentions: 10
-
⚠️ Priority: 4
-
📝 Analysis: Unauthenticated Local File Inclusion flaw found in Gladinet CentreStack and TrioFox (prior to v16.7.10368.56560). Exploitation observed in the wild. This vulnerability has a CVSS score of 6.2, with a priority score of 4 due to low EPSS and low CVSS.
2025-10-12 10:02:43
#3 · PT-2025-36080 · Google · Android
Published
2025-09-01
·
Updated
2025-10-15
·
CVE-2025-48561
5.5
Medium
Base
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Fix
Side Channel Attack
Related posts · 11
-
📝 In multiple locations, there is a possible way to access data displayed on the screen due to side channel information disclosure. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
-
📅 Published: 04/09/2025
-
📈 CVSS: 5.5
-
🧭 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
-
📣 Mentions: 2
-
⚠️ Priority: 4
-
📝 Analysis: A side channel information disclosure vulnerability exists in multiple locations, potentially allowing local data exposure without requiring additional execution privileges or user interaction. No known exploits have been detected in the wild. Given the low Exploitability Score (EPSS) and CVSS score of 5.5, this is classified as a priority 4 issue, indicating a low risk at this time.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A BitLocker security bypass vulnerability has been identified, enabling remote attackers to compromise sensitive data with moderate exploitability and high impact. While no in-the-wild activity has been confirmed yet, it is a priority 2 issue due to its high CVSS score.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A Windows BitLocker Security Feature Bypass vulnerability has been identified (CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C). Currently, no known exploits are active in the wild. Given the high CVSS score and pending analysis, it's crucial to assess potential impact on affected systems.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A Windows BitLocker Security Feature Bypass vulnerability has been identified. This issue allows unauthorized access with potential data compromise. No known exploits have been detected in the wild, but due to its high impact and moderate exploitability, it is a priority 2 vulnerability requiring attention.
-
📝 Sudo before 1.9.17p1 allows local users to obtain root access because /etc/nsswitch.conf from a user-controlled directory is used with the --chroot option.
-
📅 Published: 30/06/2025
-
📈 CVSS: 9.3
-
🛡️ CISA KEV: True
-
🧭 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
-
📣 Mentions: 75
-
⚠️ Priority: 1+
-
📝 Analysis: A local privilege escalation vulnerability exists in Sudo before 1.9.17p1, enabling local users to gain root access due to improper handling of user-controlled directories with the --chroot option. Currently, no known exploits are active in the wild, making this a priority 4 issue according to our scoring system. Please update affected systems to the latest version.
-
📝 No description available.
-
📅 Published: 05/10/2025
-
📈 CVSS: 9.8
-
🛡️ CISA KEV: True
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📣 Mentions: 38
-
⚠️ Priority: 1+
-
📝 Analysis: A critical (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) vulnerability has been identified, with no description available. As of now, no known in-the-wild activity has been reported (CISA KEV). Due to its high severity and currently low exploitability, it is classified as a priority 2 vulnerability.
-
📝 n/a
-
📈 CVSS: 9.8
-
🧭 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📝 Analysis: Debian Linux - 7zip
-
📝 n/a
-
📈 CVSS: 9.8
-
🧭 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📝 Analysis: Debian Linux - 7zip
-
📝 No description available.
-
📅 Published: 12/10/2025
-
📈 CVSS: 7.5
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
-
📣 Mentions: 13
-
⚠️ Priority: 2
-
📝 Analysis: A remote code execution vulnerability in version-unspecified software module allows attackers to execute commands; currently no exploits detected in the wild, making it a priority 2 issue due to high CVSS score but low Exploitability Scoring System (ESS) score.
-
📝 In the Linux kernel, the following vulnerability has been resolved: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice Savino says: We are writing to report that this recent patch (141d34391abbb315d68556b7c67ad97885407547) [1] can be bypassed, and a UAF can still occur when HFSC is utilized with NETEM. The patch only checks the cl->cl_nactive field to determine whether it is the first insertion or not [2], but this field is only incremented by init_vf [3]. By using HFSC_RSC (which uses init_ed) [4], it is possible to bypass the check and insert the class twice in the eltree. Under normal conditions, this would lead to an infinite loop in hfsc_dequeue for the reasons we already explained in this report [5]. However, if TBF is added as root qdisc and it is configured with a very low rate, it can be utilized to prevent packets from being dequeued. This behavior can be exploited to perform subsequent insertions in the HFSC eltree and cause a UAF. To fix both the UAF and the infinite loop, with netem as an hfsc child, check explicitly in hfsc_enqueue whether the class is already in the eltree whenever the HFSC_RSC flag is set. [1] https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=141d34391abbb315d68556b7c67ad97885407547 [2] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L1572 [3] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L677 [4] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L1574 [5] https://lore.kernel.org/netdev/8DuRWwfqjoRDLDmBMlIfbrsZg9Gx50DHJc1ilxsEBNe2D6NMoigR_eIRIG0LOjMc3r10nUUZtArXx4oZBIdUfZQrwjcQhdinnMis_0G7VEk=@willsroot.io/T/#u
-
📅 Published: 06/06/2025
-
📈 CVSS: 0
-
🧭 Vector: n/a
-
📣 Mentions: 12
-
⚠️ Priority: 4
-
📝 Analysis: A UAF vulnerability has been identified in Linux kernel's net_sched when utilizing HFSC with NETEM. The patch (141d3439) can be bypassed, causing a UAF under specific conditions involving TBF and low rates. To mitigate, explicitly check for class presence during hfsc_enqueue if the HFSC_RSC flag is set. Currently, this vulnerability has low exploitability and activity in the wild (CISA KEV: Priority 4).
2025-10-15 10:05:41
2025-10-15 00:22:33
2025-10-14 19:19:24
#4 · PT-2025-38495 · Fortra · Goanywhere Mft
Published
2025-09-11
·
Updated
2025-10-15
·
CVE-2025-10035
10
Critical
Base
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Exploit
Fix
RCE
Command Injection
Deserialization of Untrusted Data
Related posts · 281
2025-10-15 07:02:26
2025-10-14 15:57:01
2025-10-14 15:01:42
#5 · PT-2025-41795 · Amd · Epyc
Published
2025-10-13
·
Updated
2025-10-14
·
CVE-2025-0033
6.0
Medium
Base
AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:N
Fix
Improper Access Control
Related posts · 15
2025-10-14 20:19:32
2025-10-14 17:45:09
▪️ Microsoft has addressed 173 vulnerabilities, three exploited zero-days (CVE-2025-59230, CVE-2025-47827 and CVE-2025-24990) and three with PoC (CVE-2025-2884, CVE-2025-24052 and CVE-2025-0033), nine critical
▪️ Third-party: Google Chrome, Figma, Unity, Cisco, Oracle, OpenSSL, and Apple.
▪️ 𝗚𝗼𝗼𝗴𝗹𝗲 𝗖𝗵𝗿𝗼𝗺𝗲: Actively exploited zero-day (CVE-2025-1058) in V8 JavaScript engine. Also fixed heap buffer overflow in ANGLE (CVE-2025-10502).
▪️ 𝗙𝗶𝗴𝗺𝗮: Command injection (CVE-2025-53967, CVSS 7.5) in figma-developer-mcp server; patched in version 0.6.3.
▪️ 𝗨𝗻𝗶𝘁𝘆: High-severity vulnerability (CVE-2025-59489, CVSS 8.4); affects Unity 2017.1+ on Android, Windows, macOS, Linux; no exploitation observed.
▪️ 𝗖𝗶𝘀𝗰𝗼 𝗜𝗢𝗦/𝗜𝗢𝗦 𝗫𝗘: Actively exploited zero-day (CVE-2025-20352) stack-based buffer overflow in SNMP subsystem; no workarounds.
▪️ 𝗖𝗶𝘀𝗰𝗼 𝗔𝗦𝗔/𝗙𝗧𝗗: Two actively exploited RCE vulnerabilities (CVE-2025-20333, CVE-2025-20362); 48,000+ instances exposed online; ongoing large-scale attacks.
▪️ 𝗢𝗿𝗮𝗰𝗹𝗲 𝗘-𝗕𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗦𝘂𝗶𝘁𝗲: Actively exploited zero-day (CVE-2025-61882) used in Clop ransomware data theft campaign; affects versions 12.2.3–12.2.14.
▪️ 𝗢𝗽𝗲𝗻𝗦𝗦𝗟: Medium-severity flaws (CVE-2025-9230, CVE-2025-9231, CVE-2025-9232); potential private key recovery and buffer overflows; patched in versions 3.5.4, 3.4.3, 3.3.5, 3.2.6, 3.0.18, 1.0.2zm, 1.1.1zd.
▪️ 𝗔𝗽𝗽𝗹𝗲 𝗶𝗢𝗦/𝗺𝗮𝗰𝗢𝗦: 50+ vulnerabilities fixed; one actively exploited zero-day (CVE-2025-43300) in ImageIO targeted WhatsApp users; patches released across all major Apple platforms.
2025-10-14 17:42:39
#6 · PT-2025-27466 · Sudo · Sudo
Rich Mirch
·
Published
2025-06-30
·
Updated
2025-10-15
·
CVE-2025-32463
9.3
Critical
Base
AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Exploit
Fix
LPE
Related posts · 238
-
📝 In multiple locations, there is a possible way to access data displayed on the screen due to side channel information disclosure. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
-
📅 Published: 04/09/2025
-
📈 CVSS: 5.5
-
🧭 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
-
📣 Mentions: 2
-
⚠️ Priority: 4
-
📝 Analysis: A side channel information disclosure vulnerability exists in multiple locations, potentially allowing local data exposure without requiring additional execution privileges or user interaction. No known exploits have been detected in the wild. Given the low Exploitability Score (EPSS) and CVSS score of 5.5, this is classified as a priority 4 issue, indicating a low risk at this time.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A BitLocker security bypass vulnerability has been identified, enabling remote attackers to compromise sensitive data with moderate exploitability and high impact. While no in-the-wild activity has been confirmed yet, it is a priority 2 issue due to its high CVSS score.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A Windows BitLocker Security Feature Bypass vulnerability has been identified (CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C). Currently, no known exploits are active in the wild. Given the high CVSS score and pending analysis, it's crucial to assess potential impact on affected systems.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A Windows BitLocker Security Feature Bypass vulnerability has been identified. This issue allows unauthorized access with potential data compromise. No known exploits have been detected in the wild, but due to its high impact and moderate exploitability, it is a priority 2 vulnerability requiring attention.
-
📝 Sudo before 1.9.17p1 allows local users to obtain root access because /etc/nsswitch.conf from a user-controlled directory is used with the --chroot option.
-
📅 Published: 30/06/2025
-
📈 CVSS: 9.3
-
🛡️ CISA KEV: True
-
🧭 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
-
📣 Mentions: 75
-
⚠️ Priority: 1+
-
📝 Analysis: A local privilege escalation vulnerability exists in Sudo before 1.9.17p1, enabling local users to gain root access due to improper handling of user-controlled directories with the --chroot option. Currently, no known exploits are active in the wild, making this a priority 4 issue according to our scoring system. Please update affected systems to the latest version.
-
📝 No description available.
-
📅 Published: 05/10/2025
-
📈 CVSS: 9.8
-
🛡️ CISA KEV: True
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📣 Mentions: 38
-
⚠️ Priority: 1+
-
📝 Analysis: A critical (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) vulnerability has been identified, with no description available. As of now, no known in-the-wild activity has been reported (CISA KEV). Due to its high severity and currently low exploitability, it is classified as a priority 2 vulnerability.
-
📝 n/a
-
📈 CVSS: 9.8
-
🧭 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📝 Analysis: Debian Linux - 7zip
-
📝 n/a
-
📈 CVSS: 9.8
-
🧭 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📝 Analysis: Debian Linux - 7zip
-
📝 No description available.
-
📅 Published: 12/10/2025
-
📈 CVSS: 7.5
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
-
📣 Mentions: 13
-
⚠️ Priority: 2
-
📝 Analysis: A remote code execution vulnerability in version-unspecified software module allows attackers to execute commands; currently no exploits detected in the wild, making it a priority 2 issue due to high CVSS score but low Exploitability Scoring System (ESS) score.
-
📝 In the Linux kernel, the following vulnerability has been resolved: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice Savino says: We are writing to report that this recent patch (141d34391abbb315d68556b7c67ad97885407547) [1] can be bypassed, and a UAF can still occur when HFSC is utilized with NETEM. The patch only checks the cl->cl_nactive field to determine whether it is the first insertion or not [2], but this field is only incremented by init_vf [3]. By using HFSC_RSC (which uses init_ed) [4], it is possible to bypass the check and insert the class twice in the eltree. Under normal conditions, this would lead to an infinite loop in hfsc_dequeue for the reasons we already explained in this report [5]. However, if TBF is added as root qdisc and it is configured with a very low rate, it can be utilized to prevent packets from being dequeued. This behavior can be exploited to perform subsequent insertions in the HFSC eltree and cause a UAF. To fix both the UAF and the infinite loop, with netem as an hfsc child, check explicitly in hfsc_enqueue whether the class is already in the eltree whenever the HFSC_RSC flag is set. [1] https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=141d34391abbb315d68556b7c67ad97885407547 [2] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L1572 [3] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L677 [4] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L1574 [5] https://lore.kernel.org/netdev/8DuRWwfqjoRDLDmBMlIfbrsZg9Gx50DHJc1ilxsEBNe2D6NMoigR_eIRIG0LOjMc3r10nUUZtArXx4oZBIdUfZQrwjcQhdinnMis_0G7VEk=@willsroot.io/T/#u
-
📅 Published: 06/06/2025
-
📈 CVSS: 0
-
🧭 Vector: n/a
-
📣 Mentions: 12
-
⚠️ Priority: 4
-
📝 Analysis: A UAF vulnerability has been identified in Linux kernel's net_sched when utilizing HFSC with NETEM. The patch (141d3439) can be bypassed, causing a UAF under specific conditions involving TBF and low rates. To mitigate, explicitly check for class presence during hfsc_enqueue if the HFSC_RSC flag is set. Currently, this vulnerability has low exploitability and activity in the wild (CISA KEV: Priority 4).
2025-10-15 10:05:41
2025-10-15 01:18:00
2025-10-14 13:09:29
#7 · PT-2025-41705 · Oracle · Oracle Configurator
Published
2025-10-12
·
Updated
2025-10-15
·
CVE-2025-61884
7.5
High
Base
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Fix
Related posts · 84
-
📝 In multiple locations, there is a possible way to access data displayed on the screen due to side channel information disclosure. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
-
📅 Published: 04/09/2025
-
📈 CVSS: 5.5
-
🧭 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
-
📣 Mentions: 2
-
⚠️ Priority: 4
-
📝 Analysis: A side channel information disclosure vulnerability exists in multiple locations, potentially allowing local data exposure without requiring additional execution privileges or user interaction. No known exploits have been detected in the wild. Given the low Exploitability Score (EPSS) and CVSS score of 5.5, this is classified as a priority 4 issue, indicating a low risk at this time.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A BitLocker security bypass vulnerability has been identified, enabling remote attackers to compromise sensitive data with moderate exploitability and high impact. While no in-the-wild activity has been confirmed yet, it is a priority 2 issue due to its high CVSS score.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A Windows BitLocker Security Feature Bypass vulnerability has been identified (CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C). Currently, no known exploits are active in the wild. Given the high CVSS score and pending analysis, it's crucial to assess potential impact on affected systems.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A Windows BitLocker Security Feature Bypass vulnerability has been identified. This issue allows unauthorized access with potential data compromise. No known exploits have been detected in the wild, but due to its high impact and moderate exploitability, it is a priority 2 vulnerability requiring attention.
-
📝 Sudo before 1.9.17p1 allows local users to obtain root access because /etc/nsswitch.conf from a user-controlled directory is used with the --chroot option.
-
📅 Published: 30/06/2025
-
📈 CVSS: 9.3
-
🛡️ CISA KEV: True
-
🧭 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
-
📣 Mentions: 75
-
⚠️ Priority: 1+
-
📝 Analysis: A local privilege escalation vulnerability exists in Sudo before 1.9.17p1, enabling local users to gain root access due to improper handling of user-controlled directories with the --chroot option. Currently, no known exploits are active in the wild, making this a priority 4 issue according to our scoring system. Please update affected systems to the latest version.
-
📝 No description available.
-
📅 Published: 05/10/2025
-
📈 CVSS: 9.8
-
🛡️ CISA KEV: True
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📣 Mentions: 38
-
⚠️ Priority: 1+
-
📝 Analysis: A critical (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) vulnerability has been identified, with no description available. As of now, no known in-the-wild activity has been reported (CISA KEV). Due to its high severity and currently low exploitability, it is classified as a priority 2 vulnerability.
-
📝 n/a
-
📈 CVSS: 9.8
-
🧭 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📝 Analysis: Debian Linux - 7zip
-
📝 n/a
-
📈 CVSS: 9.8
-
🧭 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📝 Analysis: Debian Linux - 7zip
-
📝 No description available.
-
📅 Published: 12/10/2025
-
📈 CVSS: 7.5
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
-
📣 Mentions: 13
-
⚠️ Priority: 2
-
📝 Analysis: A remote code execution vulnerability in version-unspecified software module allows attackers to execute commands; currently no exploits detected in the wild, making it a priority 2 issue due to high CVSS score but low Exploitability Scoring System (ESS) score.
-
📝 In the Linux kernel, the following vulnerability has been resolved: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice Savino says: We are writing to report that this recent patch (141d34391abbb315d68556b7c67ad97885407547) [1] can be bypassed, and a UAF can still occur when HFSC is utilized with NETEM. The patch only checks the cl->cl_nactive field to determine whether it is the first insertion or not [2], but this field is only incremented by init_vf [3]. By using HFSC_RSC (which uses init_ed) [4], it is possible to bypass the check and insert the class twice in the eltree. Under normal conditions, this would lead to an infinite loop in hfsc_dequeue for the reasons we already explained in this report [5]. However, if TBF is added as root qdisc and it is configured with a very low rate, it can be utilized to prevent packets from being dequeued. This behavior can be exploited to perform subsequent insertions in the HFSC eltree and cause a UAF. To fix both the UAF and the infinite loop, with netem as an hfsc child, check explicitly in hfsc_enqueue whether the class is already in the eltree whenever the HFSC_RSC flag is set. [1] https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=141d34391abbb315d68556b7c67ad97885407547 [2] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L1572 [3] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L677 [4] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L1574 [5] https://lore.kernel.org/netdev/8DuRWwfqjoRDLDmBMlIfbrsZg9Gx50DHJc1ilxsEBNe2D6NMoigR_eIRIG0LOjMc3r10nUUZtArXx4oZBIdUfZQrwjcQhdinnMis_0G7VEk=@willsroot.io/T/#u
-
📅 Published: 06/06/2025
-
📈 CVSS: 0
-
🧭 Vector: n/a
-
📣 Mentions: 12
-
⚠️ Priority: 4
-
📝 Analysis: A UAF vulnerability has been identified in Linux kernel's net_sched when utilizing HFSC with NETEM. The patch (141d3439) can be bypassed, causing a UAF under specific conditions involving TBF and low rates. To mitigate, explicitly check for class presence during hfsc_enqueue if the HFSC_RSC flag is set. Currently, this vulnerability has low exploitability and activity in the wild (CISA KEV: Priority 4).
2025-10-15 10:05:41
2025-10-15 02:43:40
2025-10-15 01:29:02
#8 · PT-2025-24857 · Microsoft · Windows Smb
James Forshaw
+2
·
Published
2025-01-30
·
Updated
2025-10-15
·
CVE-2025-33073
9.0
High
Base
AV:N/AC:L/Au:S/C:C/I:C/A:C
Exploit
Fix
RCE
LPE
Improper Access Control
Related posts · 162
2025-10-14 13:48:00
2025-10-11 10:53:03
2025-10-11 07:59:10
#9 · PT-2025-40594 · Redis · Redis
Benny Isaacs
+4
·
Published
2025-10-03
·
Updated
2025-10-15
·
CVE-2025-49844
9.9
Critical
Base
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Exploit
Fix
RCE
Use After Free
Related posts · 129
2025-10-14 16:25:20
2025-10-14 09:28:40
2025-10-13 22:00:02
#10 · PT-2025-36562 · Sap · Sap Netweaver
Published
2025-09-09
·
Updated
2025-10-15
·
CVE-2025-42944
10
Critical
Base
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Fix
RCE
Deserialization of Untrusted Data
Related posts · 46
2025-10-15 07:01:43
2025-10-15 06:53:09
2025-10-15 06:23:22
#11 · PT-2025-35830 · Sitecore · Sitecore Experience Manager
Andi Slok
+4
·
Published
2025-09-03
·
Updated
2025-10-14
·
CVE-2025-53690
9.0
Critical
Base
AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Exploit
Fix
RCE
LPE
Deserialization of Untrusted Data
Related posts · 91
2025-10-14 16:30:05
2025-10-11 18:05:33
2025-10-04 04:32:29
#12 · PT-2025-41585 · Nvidia · Nvidia Gpu Display Driver For Linux
Robin Bastide
·
Published
2025-10-10
·
Updated
2025-10-14
·
CVE-2025-23280
7.0
High
Base
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
LPE
DoS
Use After Free
Related posts · 6
2025-10-14 16:37:16
2025-10-11 01:39:00
2025-10-10 19:03:46
#13 · PT-2025-39834 · Vmware · Vmware Aria Operations
Maxime Thiebaut
·
Published
2025-01-01
·
Updated
2025-10-15
·
CVE-2025-41244
7.8
High
Base
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Exploit
Fix
LPE
Related posts · 98
2025-10-14 09:28:40
2025-10-13 20:54:05
2025-10-12 06:00:13
#14 · PT-2025-42173 · Debian · Firmware-Nvidia-Gsp
Published
2025-01-01
·
Updated
2025-10-14
·
CVE-2025-23330
None
Related posts · 1
2025-10-14 16:37:16
#15 · PT-2025-42018 · Microsoft · Windows Bitlocker
Published
2025-10-14
·
Updated
2025-10-15
·
CVE-2025-55333
6.1
Medium
Base
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Related posts · 3
-
📝 In multiple locations, there is a possible way to access data displayed on the screen due to side channel information disclosure. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
-
📅 Published: 04/09/2025
-
📈 CVSS: 5.5
-
🧭 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
-
📣 Mentions: 2
-
⚠️ Priority: 4
-
📝 Analysis: A side channel information disclosure vulnerability exists in multiple locations, potentially allowing local data exposure without requiring additional execution privileges or user interaction. No known exploits have been detected in the wild. Given the low Exploitability Score (EPSS) and CVSS score of 5.5, this is classified as a priority 4 issue, indicating a low risk at this time.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A BitLocker security bypass vulnerability has been identified, enabling remote attackers to compromise sensitive data with moderate exploitability and high impact. While no in-the-wild activity has been confirmed yet, it is a priority 2 issue due to its high CVSS score.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A Windows BitLocker Security Feature Bypass vulnerability has been identified (CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C). Currently, no known exploits are active in the wild. Given the high CVSS score and pending analysis, it's crucial to assess potential impact on affected systems.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A Windows BitLocker Security Feature Bypass vulnerability has been identified. This issue allows unauthorized access with potential data compromise. No known exploits have been detected in the wild, but due to its high impact and moderate exploitability, it is a priority 2 vulnerability requiring attention.
-
📝 Sudo before 1.9.17p1 allows local users to obtain root access because /etc/nsswitch.conf from a user-controlled directory is used with the --chroot option.
-
📅 Published: 30/06/2025
-
📈 CVSS: 9.3
-
🛡️ CISA KEV: True
-
🧭 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
-
📣 Mentions: 75
-
⚠️ Priority: 1+
-
📝 Analysis: A local privilege escalation vulnerability exists in Sudo before 1.9.17p1, enabling local users to gain root access due to improper handling of user-controlled directories with the --chroot option. Currently, no known exploits are active in the wild, making this a priority 4 issue according to our scoring system. Please update affected systems to the latest version.
-
📝 No description available.
-
📅 Published: 05/10/2025
-
📈 CVSS: 9.8
-
🛡️ CISA KEV: True
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📣 Mentions: 38
-
⚠️ Priority: 1+
-
📝 Analysis: A critical (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) vulnerability has been identified, with no description available. As of now, no known in-the-wild activity has been reported (CISA KEV). Due to its high severity and currently low exploitability, it is classified as a priority 2 vulnerability.
-
📝 n/a
-
📈 CVSS: 9.8
-
🧭 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📝 Analysis: Debian Linux - 7zip
-
📝 n/a
-
📈 CVSS: 9.8
-
🧭 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📝 Analysis: Debian Linux - 7zip
-
📝 No description available.
-
📅 Published: 12/10/2025
-
📈 CVSS: 7.5
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
-
📣 Mentions: 13
-
⚠️ Priority: 2
-
📝 Analysis: A remote code execution vulnerability in version-unspecified software module allows attackers to execute commands; currently no exploits detected in the wild, making it a priority 2 issue due to high CVSS score but low Exploitability Scoring System (ESS) score.
-
📝 In the Linux kernel, the following vulnerability has been resolved: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice Savino says: We are writing to report that this recent patch (141d34391abbb315d68556b7c67ad97885407547) [1] can be bypassed, and a UAF can still occur when HFSC is utilized with NETEM. The patch only checks the cl->cl_nactive field to determine whether it is the first insertion or not [2], but this field is only incremented by init_vf [3]. By using HFSC_RSC (which uses init_ed) [4], it is possible to bypass the check and insert the class twice in the eltree. Under normal conditions, this would lead to an infinite loop in hfsc_dequeue for the reasons we already explained in this report [5]. However, if TBF is added as root qdisc and it is configured with a very low rate, it can be utilized to prevent packets from being dequeued. This behavior can be exploited to perform subsequent insertions in the HFSC eltree and cause a UAF. To fix both the UAF and the infinite loop, with netem as an hfsc child, check explicitly in hfsc_enqueue whether the class is already in the eltree whenever the HFSC_RSC flag is set. [1] https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=141d34391abbb315d68556b7c67ad97885407547 [2] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L1572 [3] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L677 [4] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L1574 [5] https://lore.kernel.org/netdev/8DuRWwfqjoRDLDmBMlIfbrsZg9Gx50DHJc1ilxsEBNe2D6NMoigR_eIRIG0LOjMc3r10nUUZtArXx4oZBIdUfZQrwjcQhdinnMis_0G7VEk=@willsroot.io/T/#u
-
📅 Published: 06/06/2025
-
📈 CVSS: 0
-
🧭 Vector: n/a
-
📣 Mentions: 12
-
⚠️ Priority: 4
-
📝 Analysis: A UAF vulnerability has been identified in Linux kernel's net_sched when utilizing HFSC with NETEM. The patch (141d3439) can be bypassed, causing a UAF under specific conditions involving TBF and low rates. To mitigate, explicitly check for class presence during hfsc_enqueue if the HFSC_RSC flag is set. Currently, this vulnerability has low exploitability and activity in the wild (CISA KEV: Priority 4).
2025-10-15 10:05:41
2025-10-14 20:36:39
2025-10-14 17:40:45
#16 · PT-2025-42023 · Microsoft · Windows Bitlocker
Published
2025-10-14
·
Updated
2025-10-14
·
CVE-2025-55338
6.1
Medium
Base
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Related posts · 2
2025-10-14 20:36:38
2025-10-14 17:40:45
#17 · PT-2025-42015 · Microsoft · Windows Bitlocker
Published
2025-10-14
·
Updated
2025-10-14
·
CVE-2025-55330
6.1
Medium
Base
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Related posts · 2
2025-10-14 18:49:08
2025-10-14 17:40:45
#18 · PT-2025-42017 · Microsoft · Windows Bitlocker
Published
2025-10-14
·
Updated
2025-10-15
·
CVE-2025-55332
6.1
Medium
Base
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Related posts · 3
-
📝 In multiple locations, there is a possible way to access data displayed on the screen due to side channel information disclosure. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
-
📅 Published: 04/09/2025
-
📈 CVSS: 5.5
-
🧭 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
-
📣 Mentions: 2
-
⚠️ Priority: 4
-
📝 Analysis: A side channel information disclosure vulnerability exists in multiple locations, potentially allowing local data exposure without requiring additional execution privileges or user interaction. No known exploits have been detected in the wild. Given the low Exploitability Score (EPSS) and CVSS score of 5.5, this is classified as a priority 4 issue, indicating a low risk at this time.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A BitLocker security bypass vulnerability has been identified, enabling remote attackers to compromise sensitive data with moderate exploitability and high impact. While no in-the-wild activity has been confirmed yet, it is a priority 2 issue due to its high CVSS score.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A Windows BitLocker Security Feature Bypass vulnerability has been identified (CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C). Currently, no known exploits are active in the wild. Given the high CVSS score and pending analysis, it's crucial to assess potential impact on affected systems.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A Windows BitLocker Security Feature Bypass vulnerability has been identified. This issue allows unauthorized access with potential data compromise. No known exploits have been detected in the wild, but due to its high impact and moderate exploitability, it is a priority 2 vulnerability requiring attention.
-
📝 Sudo before 1.9.17p1 allows local users to obtain root access because /etc/nsswitch.conf from a user-controlled directory is used with the --chroot option.
-
📅 Published: 30/06/2025
-
📈 CVSS: 9.3
-
🛡️ CISA KEV: True
-
🧭 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
-
📣 Mentions: 75
-
⚠️ Priority: 1+
-
📝 Analysis: A local privilege escalation vulnerability exists in Sudo before 1.9.17p1, enabling local users to gain root access due to improper handling of user-controlled directories with the --chroot option. Currently, no known exploits are active in the wild, making this a priority 4 issue according to our scoring system. Please update affected systems to the latest version.
-
📝 No description available.
-
📅 Published: 05/10/2025
-
📈 CVSS: 9.8
-
🛡️ CISA KEV: True
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📣 Mentions: 38
-
⚠️ Priority: 1+
-
📝 Analysis: A critical (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) vulnerability has been identified, with no description available. As of now, no known in-the-wild activity has been reported (CISA KEV). Due to its high severity and currently low exploitability, it is classified as a priority 2 vulnerability.
-
📝 n/a
-
📈 CVSS: 9.8
-
🧭 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📝 Analysis: Debian Linux - 7zip
-
📝 n/a
-
📈 CVSS: 9.8
-
🧭 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📝 Analysis: Debian Linux - 7zip
-
📝 No description available.
-
📅 Published: 12/10/2025
-
📈 CVSS: 7.5
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
-
📣 Mentions: 13
-
⚠️ Priority: 2
-
📝 Analysis: A remote code execution vulnerability in version-unspecified software module allows attackers to execute commands; currently no exploits detected in the wild, making it a priority 2 issue due to high CVSS score but low Exploitability Scoring System (ESS) score.
-
📝 In the Linux kernel, the following vulnerability has been resolved: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice Savino says: We are writing to report that this recent patch (141d34391abbb315d68556b7c67ad97885407547) [1] can be bypassed, and a UAF can still occur when HFSC is utilized with NETEM. The patch only checks the cl->cl_nactive field to determine whether it is the first insertion or not [2], but this field is only incremented by init_vf [3]. By using HFSC_RSC (which uses init_ed) [4], it is possible to bypass the check and insert the class twice in the eltree. Under normal conditions, this would lead to an infinite loop in hfsc_dequeue for the reasons we already explained in this report [5]. However, if TBF is added as root qdisc and it is configured with a very low rate, it can be utilized to prevent packets from being dequeued. This behavior can be exploited to perform subsequent insertions in the HFSC eltree and cause a UAF. To fix both the UAF and the infinite loop, with netem as an hfsc child, check explicitly in hfsc_enqueue whether the class is already in the eltree whenever the HFSC_RSC flag is set. [1] https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=141d34391abbb315d68556b7c67ad97885407547 [2] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L1572 [3] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L677 [4] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L1574 [5] https://lore.kernel.org/netdev/8DuRWwfqjoRDLDmBMlIfbrsZg9Gx50DHJc1ilxsEBNe2D6NMoigR_eIRIG0LOjMc3r10nUUZtArXx4oZBIdUfZQrwjcQhdinnMis_0G7VEk=@willsroot.io/T/#u
-
📅 Published: 06/06/2025
-
📈 CVSS: 0
-
🧭 Vector: n/a
-
📣 Mentions: 12
-
⚠️ Priority: 4
-
📝 Analysis: A UAF vulnerability has been identified in Linux kernel's net_sched when utilizing HFSC with NETEM. The patch (141d3439) can be bypassed, causing a UAF under specific conditions involving TBF and low rates. To mitigate, explicitly check for class presence during hfsc_enqueue if the HFSC_RSC flag is set. Currently, this vulnerability has low exploitability and activity in the wild (CISA KEV: Priority 4).
2025-10-15 10:05:41
2025-10-14 18:49:07
2025-10-14 17:40:45
#19 · PT-2025-42022 · Microsoft · Windows Bitlocker
Published
2025-10-14
·
Updated
2025-10-15
·
CVE-2025-55337
6.1
Medium
Base
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Related posts · 3
-
📝 In multiple locations, there is a possible way to access data displayed on the screen due to side channel information disclosure. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
-
📅 Published: 04/09/2025
-
📈 CVSS: 5.5
-
🧭 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
-
📣 Mentions: 2
-
⚠️ Priority: 4
-
📝 Analysis: A side channel information disclosure vulnerability exists in multiple locations, potentially allowing local data exposure without requiring additional execution privileges or user interaction. No known exploits have been detected in the wild. Given the low Exploitability Score (EPSS) and CVSS score of 5.5, this is classified as a priority 4 issue, indicating a low risk at this time.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A BitLocker security bypass vulnerability has been identified, enabling remote attackers to compromise sensitive data with moderate exploitability and high impact. While no in-the-wild activity has been confirmed yet, it is a priority 2 issue due to its high CVSS score.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A Windows BitLocker Security Feature Bypass vulnerability has been identified (CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C). Currently, no known exploits are active in the wild. Given the high CVSS score and pending analysis, it's crucial to assess potential impact on affected systems.
-
📝 Windows BitLocker Security Feature Bypass Vulnerability
-
📅 Published: 14/10/2025
-
📈 CVSS: 6.1
-
🧭 Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
-
📣 Mentions: 2
-
📝 Analysis: A Windows BitLocker Security Feature Bypass vulnerability has been identified. This issue allows unauthorized access with potential data compromise. No known exploits have been detected in the wild, but due to its high impact and moderate exploitability, it is a priority 2 vulnerability requiring attention.
-
📝 Sudo before 1.9.17p1 allows local users to obtain root access because /etc/nsswitch.conf from a user-controlled directory is used with the --chroot option.
-
📅 Published: 30/06/2025
-
📈 CVSS: 9.3
-
🛡️ CISA KEV: True
-
🧭 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
-
📣 Mentions: 75
-
⚠️ Priority: 1+
-
📝 Analysis: A local privilege escalation vulnerability exists in Sudo before 1.9.17p1, enabling local users to gain root access due to improper handling of user-controlled directories with the --chroot option. Currently, no known exploits are active in the wild, making this a priority 4 issue according to our scoring system. Please update affected systems to the latest version.
-
📝 No description available.
-
📅 Published: 05/10/2025
-
📈 CVSS: 9.8
-
🛡️ CISA KEV: True
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📣 Mentions: 38
-
⚠️ Priority: 1+
-
📝 Analysis: A critical (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) vulnerability has been identified, with no description available. As of now, no known in-the-wild activity has been reported (CISA KEV). Due to its high severity and currently low exploitability, it is classified as a priority 2 vulnerability.
-
📝 n/a
-
📈 CVSS: 9.8
-
🧭 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📝 Analysis: Debian Linux - 7zip
-
📝 n/a
-
📈 CVSS: 9.8
-
🧭 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
📝 Analysis: Debian Linux - 7zip
-
📝 No description available.
-
📅 Published: 12/10/2025
-
📈 CVSS: 7.5
-
🧭 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
-
📣 Mentions: 13
-
⚠️ Priority: 2
-
📝 Analysis: A remote code execution vulnerability in version-unspecified software module allows attackers to execute commands; currently no exploits detected in the wild, making it a priority 2 issue due to high CVSS score but low Exploitability Scoring System (ESS) score.
-
📝 In the Linux kernel, the following vulnerability has been resolved: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice Savino says: We are writing to report that this recent patch (141d34391abbb315d68556b7c67ad97885407547) [1] can be bypassed, and a UAF can still occur when HFSC is utilized with NETEM. The patch only checks the cl->cl_nactive field to determine whether it is the first insertion or not [2], but this field is only incremented by init_vf [3]. By using HFSC_RSC (which uses init_ed) [4], it is possible to bypass the check and insert the class twice in the eltree. Under normal conditions, this would lead to an infinite loop in hfsc_dequeue for the reasons we already explained in this report [5]. However, if TBF is added as root qdisc and it is configured with a very low rate, it can be utilized to prevent packets from being dequeued. This behavior can be exploited to perform subsequent insertions in the HFSC eltree and cause a UAF. To fix both the UAF and the infinite loop, with netem as an hfsc child, check explicitly in hfsc_enqueue whether the class is already in the eltree whenever the HFSC_RSC flag is set. [1] https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=141d34391abbb315d68556b7c67ad97885407547 [2] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L1572 [3] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L677 [4] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L1574 [5] https://lore.kernel.org/netdev/8DuRWwfqjoRDLDmBMlIfbrsZg9Gx50DHJc1ilxsEBNe2D6NMoigR_eIRIG0LOjMc3r10nUUZtArXx4oZBIdUfZQrwjcQhdinnMis_0G7VEk=@willsroot.io/T/#u
-
📅 Published: 06/06/2025
-
📈 CVSS: 0
-
🧭 Vector: n/a
-
📣 Mentions: 12
-
⚠️ Priority: 4
-
📝 Analysis: A UAF vulnerability has been identified in Linux kernel's net_sched when utilizing HFSC with NETEM. The patch (141d3439) can be bypassed, causing a UAF under specific conditions involving TBF and low rates. To mitigate, explicitly check for class presence during hfsc_enqueue if the HFSC_RSC flag is set. Currently, this vulnerability has low exploitability and activity in the wild (CISA KEV: Priority 4).
2025-10-15 10:05:41
2025-10-14 18:49:07
2025-10-14 17:40:45
#20 · PT-2025-42032 · Microsoft · Windows Bitlocker
Published
2025-10-14
·
Updated
2025-10-14
·
CVE-2025-55682
6.1
Medium
Base
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Related posts · 2
2025-10-14 18:49:06
2025-10-14 17:40:45
#21 · PT-2025-31937 · Ictbroadcast
Valentin Lobstein
·
Published
2025-08-05
·
Updated
2025-10-15
·
CVE-2025-2611
9.3
Critical
Base
AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit
Fix
RCE
Related posts · 8
2025-10-15 08:01:43
2025-10-15 06:17:16
2025-10-14 16:34:12
#22 · PT-2025-11082 · Zimbra · Zimbra Collaboration
Published
2025-01-27
·
Updated
2025-10-14
·
CVE-2025-27915
5.5
Medium
Base
AV:N/AC:L/Au:S/C:P/I:P/A:N
Exploit
Fix
RCE
XSS
Related posts · 44
2025-10-14 09:28:40
2025-10-13 20:30:12
2025-10-12 13:36:29
#23 · PT-2025-25212 · Microsoft · M365 Copilot
Es7Evam
+1
·
Published
2025-06-11
·
Updated
2025-10-14
·
CVE-2025-32711
9.3
Critical
Base
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
Command Injection
Related posts · 76
2025-10-14 21:50:00
2025-10-14 20:15:00
2025-10-14 13:05:00
#24 · PT-2025-41785 · Elastic · Cloud Enterprise
Published
2025-10-13
·
Updated
2025-10-14
·
CVE-2025-37729
9.1
Critical
Base
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Fix
RCE
Related posts · 14
2025-10-14 10:06:57
2025-10-14 07:15:32
2025-10-14 07:01:47
#25 · PT-2025-40939 · Openbsd · Openssh
David Leadbeater
·
Published
2025-10-06
·
Updated
2025-10-15
·
CVE-2025-61984
3.6
Low
Base
AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
ProxyCommand
is used. Specifically, the issue arises from the unsafe handling of control characters, such as newlines, in usernames. This allows an attacker to inject commands via the `ProxyCo...Exploit
Fix
RCE
Related posts · 34
2025-10-14 09:28:40
2025-10-14 05:30:30
2025-10-13 22:04:07
#26 · PT-2025-37259 · Microsoft · Windows 11
Published
2025-09-11
·
Updated
2025-10-15
·
CVE-2025-8061
7.0
High
Base
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Fix
LPE
Related posts · 13
2025-10-15 01:51:38
- Vulnerability identified as CVE-2025-8061 due to insufficient access controls in Lenovo Dispatcher drivers.
- Affected systems include older Lenovo consumer notebooks with driver versions 3.0 and 3.1.
- Proof-of-concept exploit demonstrates easy exploitation by local attackers, highlighting serious security risks.
- Lenovo has released patches for the vulnerability, urging users to update to version 3.1.0.41 or later.
- Users should enable Windows Core Isolation Memory Integrity to further mitigate risks.
2025-10-14 07:05:40
2025-10-12 13:28:01
#27 · PT-2025-21007 · Microsoft · Outlook
Haifei Li
·
Published
2025-05-13
·
Updated
2025-10-14
·
CVE-2025-32705
7.8
High
Base
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
RCE
Out of bounds Read
Related posts · 10
- Microsoft Word Remote Code Execution Vulnerability (CVE-2025-59221) https://t.co/xv55zoKIVm
- Microsoft Word Remote Code Execution Vulnerability (CVE-2025-59222) https://t.co/sXxQUQQqYw
- Word RCE, CVE-2025-59221
- Word RCE, CVE-2025-59222
- Word RCE, CVE-2025-53738
- Word RCE, CVE-2025-53784
- Word RCE, CVE-2025-49699
- Word RCE, CVE-2025-49700
- Word RCE/heap-overflow, CVE-2025-32717
- Word RCE, CVE-2025-47170
- Word RCE, CVE-2025-47957
- Outlook RCE, CVE-2025-32705
- PowerPoint RCE, CVE-2025-29978
- Word RCE, CVE-2025-29820
- Word RCE, CVE-2025-26629
- Word RCE, CVE-2025-24077
- Word RCE, CVE-2025-24078
- Word RCE, CVE-2025-24079
- Word RCE, CVE-2025-24080
- Word RCE, CVE-2025-21392
- Word RCE, CVE-2025-21397
2025-10-14 21:39:49
2025-08-03 18:37:56
2025-05-15 10:00:11
#28 · PT-2025-21253 · Node.Js · Node.Js
Panva
+1
·
Published
2025-01-01
·
Updated
2025-10-14
·
CVE-2025-23166
7.8
High
Base
AV:N/AC:L/Au:N/C:N/I:N/A:C
SignTraits::DeriveBits()
function. This flaw can be triggered by malformed crypto input in background threads, leading to a denial-of-service condition. The issue arises from an incorrect call to ThrowException()
based on user-supplied inputs. Approximately...Fix
DoS
Related posts · 20
2025-10-14 20:38:43
2025-06-11 20:53:23
2025-05-20 10:45:17
#29 · PT-2025-32858 · Microsoft · Office Word
Haifei Li
·
Published
2025-08-12
·
Updated
2025-10-14
·
CVE-2025-53784
8.4
High
Base
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
RCE
Use After Free
Related posts · 9
- Microsoft Word Remote Code Execution Vulnerability (CVE-2025-59221) https://t.co/xv55zoKIVm
- Microsoft Word Remote Code Execution Vulnerability (CVE-2025-59222) https://t.co/sXxQUQQqYw
- Word RCE, CVE-2025-59221
- Word RCE, CVE-2025-59222
- Word RCE, CVE-2025-53738
- Word RCE, CVE-2025-53784
- Word RCE, CVE-2025-49699
- Word RCE, CVE-2025-49700
- Word RCE/heap-overflow, CVE-2025-32717
- Word RCE, CVE-2025-47170
- Word RCE, CVE-2025-47957
- Outlook RCE, CVE-2025-32705
- PowerPoint RCE, CVE-2025-29978
- Word RCE, CVE-2025-29820
- Word RCE, CVE-2025-26629
- Word RCE, CVE-2025-24077
- Word RCE, CVE-2025-24078
- Word RCE, CVE-2025-24079
- Word RCE, CVE-2025-24080
- Word RCE, CVE-2025-21392
- Word RCE, CVE-2025-21397
2025-10-14 21:39:49
2025-08-15 09:55:58
2025-08-13 15:12:23
#30 · PT-2025-10823 · Microsoft · Office
Haifei Li
·
Published
2025-03-11
·
Updated
2025-10-14
·
CVE-2025-24080
7.8
High
Base
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
RCE
Use After Free
Related posts · 6
- Microsoft Word Remote Code Execution Vulnerability (CVE-2025-59221) https://t.co/xv55zoKIVm
- Microsoft Word Remote Code Execution Vulnerability (CVE-2025-59222) https://t.co/sXxQUQQqYw
- Word RCE, CVE-2025-59221
- Word RCE, CVE-2025-59222
- Word RCE, CVE-2025-53738
- Word RCE, CVE-2025-53784
- Word RCE, CVE-2025-49699
- Word RCE, CVE-2025-49700
- Word RCE/heap-overflow, CVE-2025-32717
- Word RCE, CVE-2025-47170
- Word RCE, CVE-2025-47957
- Outlook RCE, CVE-2025-32705
- PowerPoint RCE, CVE-2025-29978
- Word RCE, CVE-2025-29820
- Word RCE, CVE-2025-26629
- Word RCE, CVE-2025-24077
- Word RCE, CVE-2025-24078
- Word RCE, CVE-2025-24079
- Word RCE, CVE-2025-24080
- Word RCE, CVE-2025-21392
- Word RCE, CVE-2025-21397
2025-10-14 21:39:49
2025-07-02 14:56:53
2025-03-15 08:25:56