##
Updated at UTC 2025-12-05T23:01:39.116785
| CVE | CVSS | EPSS | Posts | Repos | Nuclei | Updated | Description |
|---|---|---|---|---|---|---|---|
| CVE-2025-14108 | 8.8 | 0.00% | 2 | 0 | 2025-12-05T22:15:49.383000 | A weakness has been identified in ZSPACE Q2C NAS up to 1.1.0210050. Affected by | |
| CVE-2025-14107 | 8.8 | 0.00% | 2 | 0 | 2025-12-05T22:15:49.163000 | A security flaw has been discovered in ZSPACE Q2C NAS up to 1.1.0210050. Affecte | |
| CVE-2025-14106 | 8.8 | 0.00% | 2 | 0 | 2025-12-05T22:15:48.950000 | A vulnerability was identified in ZSPACE Q2C NAS up to 1.1.0210050. Affected is | |
| CVE-2025-59775 | 7.5 | 0.02% | 2 | 0 | 2025-12-05T21:31:28 | Server-Side Request Forgery (SSRF) vulnerability in Apache HTTP Server on Win | |
| CVE-2025-55753 | 7.5 | 0.01% | 2 | 0 | 2025-12-05T21:31:27 | An integer overflow in the case of failed ACME certificate renewal leads, after | |
| CVE-2025-14105 | 4.3 | 0.00% | 2 | 0 | 2025-12-05T21:15:53.120000 | A vulnerability was determined in TOZED ZLT M30S and ZLT M30S PRO 1.47/3.09.06. | |
| CVE-2025-65082 | 6.5 | 0.02% | 2 | 0 | 2025-12-05T20:15:57.703000 | Improper Neutralization of Escape, Meta, or Control Sequences vulnerability in A | |
| CVE-2025-53963 | 9.8 | 0.02% | 2 | 0 | 2025-12-05T20:15:55.390000 | An issue was discovered on Thermo Fisher Ion Torrent OneTouch 2 INS1005527 devic | |
| CVE-2025-66644 | 7.2 | 0.00% | 2 | 0 | 2025-12-05T19:15:53.293000 | Array Networks ArrayOS AG before 9.4.5.9 allows command injection, as exploited | |
| CVE-2025-65346 | None | 0.07% | 2 | 1 | 2025-12-05T18:59:02 | alexusmai laravel-file-manager 3.3.1 and below is vulnerable to Directory Traver | |
| CVE-2025-66399 | 8.8 | 0.07% | 1 | 0 | 2025-12-05T18:57:11.903000 | Cacti is an open source performance and fault management framework. Prior to 1.2 | |
| CVE-2025-65955 | 4.9 | 0.01% | 1 | 0 | 2025-12-05T18:56:23.270000 | ImageMagick is free and open-source software used for editing and manipulating d | |
| CVE-2025-13354 | 4.3 | 0.03% | 1 | 0 | 2025-12-05T18:41:56.647000 | The Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI plugin for W | |
| CVE-2025-13359 | 6.5 | 0.03% | 1 | 0 | 2025-12-05T18:37:12.593000 | The Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI plugin for W | |
| CVE-2025-58098 | 8.3 | 0.00% | 2 | 0 | 2025-12-05T18:32:14 | Apache HTTP Server 2.4.65 and earlier with Server Side Includes (SSI) enabled an | |
| CVE-2025-66200 | 5.4 | 0.02% | 2 | 0 | 2025-12-05T18:15:57.067000 | mod_userdir+suexec bypass via AllowOverride FileInfo vulnerability in Apache HTT | |
| CVE-2025-55182 | 10.0 | 13.81% | 144 | 100 | template | 2025-12-05T17:44:58.770000 | A pre-authentication remote code execution vulnerability exists in React Server |
| CVE-2025-14104 | 6.1 | 0.00% | 2 | 0 | 2025-12-05T17:16:03.117000 | A flaw was found in util-linux. This vulnerability allows a heap buffer overread | |
| CVE-2025-14094 | 4.7 | 0.00% | 2 | 0 | 2025-12-05T17:16:02.917000 | A flaw has been found in Edimax BR-6478AC V3 1.0.15. The affected element is the | |
| CVE-2025-14093 | 4.7 | 0.00% | 2 | 0 | 2025-12-05T17:16:02.713000 | A vulnerability was detected in Edimax BR-6478AC V3 1.0.15. Impacted is the func | |
| CVE-2025-33211 | 7.5 | 0.04% | 1 | 0 | 2025-12-05T16:33:46.797000 | NVIDIA Triton Server for Linux contains a vulnerability where an attacker may ca | |
| CVE-2025-65730 | 0 | 0.00% | 2 | 0 | 2025-12-05T16:15:50.773000 | Authentication Bypass via Hardcoded Credentials GoAway up to v0.62.18, fixed in | |
| CVE-2025-14092 | 4.7 | 0.00% | 2 | 0 | 2025-12-05T16:15:49.540000 | A security vulnerability has been detected in Edimax BR-6478AC V3 1.0.15. This i | |
| CVE-2025-66222 | 9.6 | 0.15% | 1 | 0 | 2025-12-05T15:37:59.973000 | DeepChat is a smart assistant uses artificial intelligence. In 0.5.0 and earlier | |
| CVE-2025-13946 | 5.5 | 0.01% | 1 | 0 | 2025-12-05T15:10:25.093000 | MEGACO dissector infinite loop in Wireshark 4.6.0 to 4.6.1 and 4.4.0 to 4.4.11 a | |
| CVE-2025-13614 | 8.1 | 0.03% | 1 | 0 | 2025-12-05T12:30:19 | The Cool Tag Cloud plugin for WordPress is vulnerable to Stored Cross-Site Scrip | |
| CVE-2025-12850 | 7.5 | 0.06% | 1 | 0 | 2025-12-05T07:16:11.350000 | The My auctions allegro plugin for WordPress is vulnerable to SQL Injection via | |
| CVE-2025-12374 | 9.8 | 0.19% | 1 | 0 | 2025-12-05T07:16:11.117000 | The Email Verification, Email OTP, Block Spam Email, Passwordless login, Hide Lo | |
| CVE-2025-13066 | 8.8 | 0.10% | 1 | 0 | 2025-12-05T06:31:32 | The Demo Importer Plus plugin for WordPress is vulnerable to arbitrary file uplo | |
| CVE-2025-13313 | 9.8 | 0.12% | 1 | 0 | 2025-12-05T06:31:30 | The CRM Memberships plugin for WordPress is vulnerable to privilege escalation v | |
| CVE-2025-1547 | None | 0.04% | 2 | 0 | 2025-12-05T00:31:11 | A stack-based buffer overflow vulnerability [CWE-121] in WatchGuard Fireware OS' | |
| CVE-2025-6946 | None | 0.04% | 2 | 0 | 2025-12-05T00:31:11 | Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site | |
| CVE-2025-11838 | None | 0.07% | 2 | 0 | 2025-12-05T00:31:11 | A memory corruption vulnerability in WatchGuard Fireware OS may allow an unauthe | |
| CVE-2025-12026 | None | 0.05% | 2 | 0 | 2025-12-05T00:31:11 | An Out-of-bounds Write vulnerability in WatchGuard Fireware OS’s certificate req | |
| CVE-2025-12196 | None | 0.06% | 2 | 0 | 2025-12-05T00:31:11 | An Out-of-bounds Write vulnerability in WatchGuard Fireware OS's CLI could allow | |
| CVE-2024-3884 | 7.5 | 0.48% | 2 | 0 | 2025-12-04T23:15:45.300000 | A flaw was found in Undertow that can cause remote denial of service attacks. Wh | |
| CVE-2025-1910 | 0 | 0.01% | 2 | 0 | 2025-12-04T22:15:48.583000 | The WatchGuard Mobile VPN with SSL Client on Windows allows a locally authentic | |
| CVE-2025-1545 | 0 | 0.17% | 2 | 0 | 2025-12-04T22:15:48.290000 | An XPath Injection vulnerability in WatchGuard Fireware OS may allow a remote un | |
| CVE-2025-13940 | 0 | 0.01% | 2 | 0 | 2025-12-04T22:15:48.140000 | An Expected Behavior Violation [CWE-440] vulnerability in WatchGuard Fireware OS | |
| CVE-2025-13939 | 0 | 0.04% | 2 | 0 | 2025-12-04T22:15:48 | Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site | |
| CVE-2025-13938 | 0 | 0.04% | 2 | 0 | 2025-12-04T22:15:47.863000 | Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site | |
| CVE-2025-13937 | 0 | 0.04% | 2 | 0 | 2025-12-04T22:15:47.697000 | Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site | |
| CVE-2025-13936 | 0 | 0.04% | 2 | 0 | 2025-12-04T22:15:47.520000 | Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site | |
| CVE-2025-12195 | 0 | 0.06% | 2 | 0 | 2025-12-04T22:15:46.920000 | An Out-of-bounds Write vulnerability in WatchGuard Fireware OS's CLI could allow | |
| CVE-2025-66571 | None | 0.18% | 1 | 0 | 2025-12-04T21:31:17 | UNA CMS versions 9.0.0-RC1 - 14.0.0-RC4 contain a PHP object injection vulnerabi | |
| CVE-2025-29269 | None | 0.13% | 2 | 0 | 2025-12-04T21:31:12 | ALLNET ALL-RUT22GW v3.3.8 was discovered to contain an OS command injection vuln | |
| CVE-2025-29268 | None | 0.02% | 2 | 0 | 2025-12-04T21:31:06 | ALLNET ALL-RUT22GW v3.3.8 was discovered to store hardcoded credentials in the l | |
| CVE-2025-65883 | None | 0.07% | 2 | 0 | 2025-12-04T21:31:06 | A vulnerability has been identified in Genexis Platinum P4410 router (Firmware P | |
| CVE-2025-13638 | 8.8 | 0.10% | 1 | 0 | 2025-12-04T19:20:42.487000 | Use after free in Media Stream in Google Chrome prior to 143.0.7499.41 allowed a | |
| CVE-2025-66373 | None | 0.02% | 2 | 0 | 2025-12-04T18:31:01 | Akamai Ghost on Akamai CDN edge servers before 2025-11-17 has a chunked request | |
| CVE-2025-66287 | 8.8 | 0.04% | 2 | 0 | 2025-12-04T18:31:01 | A flaw was found in WebKitGTK. Processing malicious web content can cause an une | |
| CVE-2025-13720 | 8.8 | 0.07% | 1 | 0 | 2025-12-04T18:06:43.940000 | Bad cast in Loader in Google Chrome prior to 143.0.7499.41 allowed a remote atta | |
| CVE-2025-66516 | 0 | 0.05% | 5 | 0 | 2025-12-04T17:15:57.120000 | Critical XXE in Apache Tika tika-core (1.13-3.2.1), tika-pdf-module (2.0.0-3.2.1 | |
| CVE-2025-66293 | 7.1 | 0.04% | 2 | 0 | 2025-12-04T17:15:08.283000 | LIBPNG is a reference library for use in applications that read, create, and man | |
| CVE-2025-50360 | 8.4 | 0.01% | 2 | 1 | 2025-12-04T17:15:08.283000 | A heap buffer overflow in compiler.c and compiler.h in Pepper language 0.1.1comm | |
| CVE-2025-13342 | 9.8 | 0.04% | 2 | 0 | 2025-12-04T17:15:08.283000 | The Frontend Admin by DynamiApps plugin for WordPress is vulnerable to unauthori | |
| CVE-2025-13756 | 4.3 | 0.03% | 1 | 0 | 2025-12-04T17:15:08.283000 | The Fluent Booking plugin for WordPress is vulnerable to unauthorized calendar i | |
| CVE-2025-13947 | 7.4 | 0.04% | 1 | 0 | 2025-12-04T17:15:08.283000 | A flaw was found in WebKitGTK. This vulnerability allows remote, user-assisted i | |
| CVE-2025-29864 | 0 | 0.02% | 1 | 0 | 2025-12-04T17:15:08.283000 | Protection Mechanism Failure vulnerability in ESTsoft ALZip on Windows allows Sm | |
| CVE-2025-13472 | 0 | 0.03% | 1 | 0 | 2025-12-04T17:15:08.283000 | A fix was made in BlazeMeter Jenkins Plugin version 4.27 to allow users only wit | |
| CVE-2025-13486 | 9.8 | 0.25% | 2 | 5 | 2025-12-04T17:15:08.283000 | The Advanced Custom Fields: Extended plugin for WordPress is vulnerable to Remot | |
| CVE-2025-12954 | 2.7 | 0.02% | 1 | 0 | 2025-12-04T17:15:08.283000 | The Timetable and Event Schedule by MotoPress WordPress plugin before 2.4.16 doe | |
| CVE-2025-12585 | 5.3 | 0.04% | 1 | 1 | 2025-12-04T17:15:08.283000 | The MxChat – AI Chatbot for WordPress plugin for WordPress is vulnerable to Sens | |
| CVE-2025-13646 | 7.5 | 0.19% | 1 | 0 | 2025-12-04T17:15:08.283000 | The Modula Image Gallery plugin for WordPress is vulnerable to arbitrary file up | |
| CVE-2025-13448 | 6.4 | 0.03% | 1 | 0 | 2025-12-04T17:15:08.283000 | The CSSIgniter Shortcodes plugin for WordPress is vulnerable to Stored Cross-Sit | |
| CVE-2025-66476 | 7.8 | 0.01% | 1 | 0 | 2025-12-04T17:15:08.283000 | Vim is an open source, command line text editor. Prior to version 9.1.1947, an u | |
| CVE-2025-64298 | 8.4 | 0.01% | 2 | 0 | 2025-12-04T17:15:08.283000 | NMIS/BioDose V22.02 and previous version installations where the embedded Micros | |
| CVE-2025-62575 | 8.3 | 0.18% | 2 | 0 | 2025-12-04T17:15:08.283000 | NMIS/BioDose V22.02 and previous versions rely on a Microsoft SQL Server databas | |
| CVE-2025-65877 | 6.5 | 0.03% | 1 | 0 | 2025-12-04T17:15:08.283000 | Lvzhou CMS before commit c4ea0eb9cab5f6739b2c87e77d9ef304017ed615 (2025-09-22) i | |
| CVE-2025-33208 | 8.8 | 0.03% | 1 | 0 | 2025-12-04T17:15:08.283000 | NVIDIA TAO contains a vulnerability where an attacker may cause a resource to be | |
| CVE-2025-12819 | 7.5 | 0.06% | 1 | 0 | 2025-12-04T00:32:03 | Untrusted search path in auth_query connection handler in PgBouncer before 1.25. | |
| CVE-2021-26828 | 8.8 | 80.12% | 8 | 3 | 2025-12-03T21:32:01 | OpenPLC ScadaBR through 0.9.1 on Linux and through 1.12.4 on Windows allows remo | |
| CVE-2025-50361 | 5.1 | 0.01% | 2 | 1 | 2025-12-03T21:31:11 | Buffer Overflow was found in SmallBASIC community SmallBASIC with SDL Before v12 | |
| CVE-2025-13086 | None | 0.04% | 4 | 0 | 2025-12-03T21:31:11 | Improper validation of source IP addresses in OpenVPN version 2.6.0 through 2.7_ | |
| CVE-2025-33201 | 7.5 | 0.04% | 1 | 0 | 2025-12-03T21:31:10 | NVIDIA Triton Inference Server contains a vulnerability where an attacker may ca | |
| CVE-2025-41012 | 5.3 | 0.05% | 1 | 0 | 2025-12-03T21:31:04 | Unauthorized access vulnerability in TCMAN GIM v11 version 20250304. This vulner | |
| CVE-2025-11788 | 9.8 | 0.04% | 1 | 0 | 2025-12-03T21:31:04 | Heap-based buffer overflow vulnerability in Circutor SGE-PLC1000/SGE-PLC50 v9.0. | |
| CVE-2025-65358 | 9.8 | 0.03% | 1 | 0 | 2025-12-03T20:22:29.533000 | Edoc-doctor-appointment-system v1.0.1 was discovered to contain SQl injection vu | |
| CVE-2025-41013 | 9.8 | 0.03% | 1 | 0 | 2025-12-03T19:54:41.300000 | SQL injection vulnerability in TCMAN GIM v11 in version 20250304. This vulnerabi | |
| CVE-2025-11787 | 8.8 | 0.21% | 1 | 0 | 2025-12-03T19:16:37.603000 | Command injection vulnerability in the operating system in Circutor SGE-PLC1000/ | |
| CVE-2025-34319 | None | 1.84% | 1 | 0 | 2025-12-03T18:30:37 | TOTOLINK N300RT wireless router firmware versions prior to V3.4.0-B20250430 (dis | |
| CVE-2025-66431 | 7.9 | 0.03% | 2 | 0 | 2025-12-03T18:30:37 | WebPros Plesk before 18.0.73.5 and 18.0.74 before 18.0.74.2 on Linux allows remo | |
| CVE-2025-13390 | 10.0 | 0.25% | 1 | 2 | 2025-12-03T18:30:24 | The WP Directory Kit plugin for WordPress is vulnerable to authentication bypass | |
| CVE-2025-66478 | 0 | 0.00% | 37 | 23 | 2025-12-03T18:15:47.200000 | Rejected reason: This CVE is a duplicate of CVE-2025-55182. | |
| CVE-2025-65657 | 6.5 | 0.08% | 1 | 0 | 2025-12-03T16:59:22 | FeehiCMS version 2.1.1 has a Remote Code Execution via Unrestricted File Upload | |
| CVE-2025-65656 | 9.8 | 0.04% | 1 | 0 | 2025-12-03T15:31:32 | dcat-admin v2.2.3-beta and before is vulnerable to file inclusion in admin/src/E | |
| CVE-2025-60854 | 9.8 | 0.27% | 1 | 0 | 2025-12-03T15:31:32 | A vulnerability has been found in D-Link R15 (AX1500) 1.20.01 and below. By mani | |
| CVE-2025-13949 | 6.3 | 0.03% | 1 | 0 | 2025-12-03T15:30:36 | A vulnerability was identified in ProudMuBai GoFilm 1.0.0/1.0.1. Impacted is the | |
| CVE-2025-13948 | 5.6 | 0.04% | 1 | 0 | 2025-12-03T15:30:36 | A vulnerability was determined in opsre go-ldap-admin up to 20251011. This issue | |
| CVE-2025-13401 | 6.4 | 0.03% | 1 | 0 | 2025-12-03T15:30:36 | The Autoptimize plugin for WordPress is vulnerable to Stored Cross-Site Scriptin | |
| CVE-2025-13109 | 4.3 | 0.03% | 1 | 0 | 2025-12-03T15:30:36 | The HUSKY – Products Filter Professional for WooCommerce plugin for WordPress is | |
| CVE-2025-12887 | 5.4 | 0.04% | 1 | 0 | 2025-12-03T15:30:36 | The Post SMTP plugin for WordPress is vulnerable to authorization bypass in all | |
| CVE-2025-65186 | 6.1 | 0.03% | 1 | 0 | 2025-12-03T14:18:29 | Grav CMS 1.7.49 is vulnerable to Cross Site Scripting (XSS). The page editor all | |
| CVE-2025-39665 | None | 0.07% | 1 | 0 | 2025-12-03T12:30:20 | User enumeration in Nagvis' Checkmk MultisiteAuth before version 1.9.48 allows a | |
| CVE-2025-13945 | 5.5 | 0.01% | 1 | 0 | 2025-12-03T09:31:18 | HTTP3 dissector crash in Wireshark 4.6.0 and 4.6.1 allows denial of service | |
| CVE-2025-12744 | 8.8 | 0.02% | 2 | 1 | 2025-12-03T09:31:13 | A flaw was found in the ABRT daemon’s handling of user-supplied mount informatio | |
| CVE-2025-13495 | 4.9 | 0.02% | 1 | 0 | 2025-12-03T06:31:20 | The FluentCart plugin for WordPress is vulnerable to SQL Injection via the 'grou | |
| CVE-2025-10304 | 5.3 | 0.06% | 1 | 0 | 2025-12-03T06:31:16 | The Everest Backup – WordPress Cloud Backup, Migration, Restore & Cloning Plugin | |
| CVE-2025-13645 | 7.2 | 0.65% | 1 | 0 | 2025-12-03T03:31:21 | The Modula Image Gallery plugin for WordPress is vulnerable to arbitrary file de | |
| CVE-2025-55181 | 5.3 | 0.04% | 1 | 0 | 2025-12-03T03:31:21 | Sending an HTTP request/response body with greater than 2^31 bytes triggers an i | |
| CVE-2025-65380 | 6.5 | 0.02% | 1 | 0 | 2025-12-03T00:31:35 | PHPGurukul Billing System 1.0 is vulnerable to SQL Injection in the admin/index. | |
| CVE-2025-65379 | 6.5 | 0.02% | 1 | 0 | 2025-12-03T00:31:35 | PHPGurukul Billing System 1.0 is vulnerable to SQL Injection in the /admin/passw | |
| CVE-2025-64460 | 7.5 | 0.03% | 1 | 0 | 2025-12-02T22:16:08.850000 | An issue was discovered in 5.2 before 5.2.9, 5.1 before 5.1.15, and 4.2 before 4 | |
| CVE-2025-64070 | 5.4 | 0.03% | 1 | 0 | 2025-12-02T21:32:34 | Sourcecodester Student Grades Management System v1.0 is vulnerable to Cross Site | |
| CVE-2022-50266 | 5.5 | 0.02% | 2 | 0 | 2025-12-02T21:32:33 | In the Linux kernel, the following vulnerability has been resolved: kprobes: Fi | |
| CVE-2025-13658 | None | 0.08% | 4 | 0 | 2025-12-02T21:31:42 | A vulnerability in Longwatch devices allows unauthenticated HTTP GET requests to | |
| CVE-2025-64778 | 7.3 | 0.01% | 2 | 0 | 2025-12-02T21:31:42 | NMIS/BioDose software V22.02 and previous versions contain executable binaries w | |
| CVE-2025-64642 | 8.0 | 0.01% | 2 | 0 | 2025-12-02T21:31:42 | NMIS/BioDose V22.02 and previous versions' installation directory paths by defau | |
| CVE-2025-61940 | 8.3 | 0.07% | 2 | 0 | 2025-12-02T21:31:42 | NMIS/BioDose V22.02 and previous versions rely on a common SQL Server user accou | |
| CVE-2025-13510 | None | 0.09% | 2 | 0 | 2025-12-02T21:31:37 | The Iskra iHUB and iHUB Lite smart metering gateway exposes its web management i | |
| CVE-2025-13542 | 9.8 | 0.07% | 1 | 0 | 2025-12-02T21:31:37 | The DesignThemes LMS plugin for WordPress is vulnerable to Privilege Escalation | |
| CVE-2025-57850 | 5.2 | 0.00% | 1 | 0 | 2025-12-02T21:31:37 | A container privilege escalation flaw was found in certain CodeReady Workspaces | |
| CVE-2025-34352 | None | 0.02% | 1 | 0 | 2025-12-02T21:31:37 | JumpCloud Remote Assist for Windows versions prior to 0.317.0 include an uninsta | |
| CVE-2025-13827 | None | 0.27% | 2 | 0 | 2025-12-02T21:11:36 | ### Summary Arbitrary files can be uploaded via the GrapesJS Builder, as the ty | |
| CVE-2025-64750 | 4.5 | 0.01% | 1 | 0 | 2025-12-02T21:07:03 | ### Impact _**Native Mode (default)**_ Singularity's default native runtime al | |
| CVE-2023-53261 | 5.5 | 0.02% | 2 | 0 | 2025-12-02T20:45:00.577000 | In the Linux kernel, the following vulnerability has been resolved: coresight: | |
| CVE-2025-65187 | 6.1 | 0.03% | 1 | 0 | 2025-12-02T20:15:52.670000 | A Stored Cross Site Scripting vulnerability exists in CiviCRM before v6.7 in the | |
| CVE-2025-63872 | 6.1 | 0.04% | 1 | 0 | 2025-12-02T20:15:51.837000 | DeepSeek V3.2 has a Cross Site Scripting (XSS) vulnerability, which allows JavaS | |
| CVE-2023-53292 | 5.5 | 0.02% | 2 | 0 | 2025-12-02T19:07:08.450000 | In the Linux kernel, the following vulnerability has been resolved: blk-mq: fix | |
| CVE-2025-13828 | 0 | 0.04% | 2 | 0 | 2025-12-02T17:16:29.163000 | SummaryA non privileged user can install and remove arbitrary packages via compo | |
| CVE-2025-12106 | 9.1 | 0.06% | 1 | 0 | 2025-12-01T21:31:27 | Insufficient argument validation in OpenVPN 2.7_alpha1 through 2.7_rc1 allows an | |
| CVE-2021-26829 | 5.4 | 32.79% | 1 | 0 | 2025-12-01T15:23:18.697000 | OpenPLC ScadaBR through 0.9.1 on Linux and through 1.12.4 on Windows allows stor | |
| CVE-2025-6389 | 9.8 | 0.34% | 2 | 1 | 2025-11-25T03:30:26 | The Sneeit Framework plugin for WordPress is vulnerable to Remote Code Execution | |
| CVE-2018-25126 | None | 1.56% | 1 | 0 | 2025-11-24T21:31:06 | Shenzhen TVT Digital Technology Co., Ltd. NVMS-9000 firmware (used by many white | |
| CVE-2025-11001 | 7.8 | 0.29% | 2 | 6 | 2025-11-24T15:07:32.807000 | 7-Zip ZIP File Parsing Directory Traversal Remote Code Execution Vulnerability. | |
| CVE-2025-20304 | 5.4 | 0.04% | 2 | 0 | 2025-11-19T21:56:39.907000 | Multiple vulnerabilities in the web-based management interface of Cisco ISE and | |
| CVE-2025-20289 | 4.8 | 0.04% | 2 | 0 | 2025-11-19T15:13:13.230000 | Multiple vulnerabilities in the web-based management interface of Cisco ISE and | |
| CVE-2015-5119 | 9.8 | 93.08% | 1 | 4 | 2025-11-17T21:32:22 | Use-after-free vulnerability in the ByteArray class in the ActionScript 3 (AS3) | |
| CVE-2025-10157 | 7.8 | 0.20% | 3 | 0 | 2025-11-13T17:02:36.447000 | A Protection Mechanism Failure vulnerability in mmaitre314 picklescan versions u | |
| CVE-2025-12443 | 4.3 | 0.03% | 2 | 0 | 2025-11-11T00:30:20 | Out of bounds read in WebXR in Google Chrome prior to 142.0.7444.59 allowed a re | |
| CVE-2025-34299 | None | 11.03% | 2 | 3 | 2025-11-07T15:31:36 | Monsta FTP versions 2.11 and earlier contain a vulnerability that allows unauthe | |
| CVE-2025-9491 | 7.8 | 0.23% | 9 | 1 | 2025-11-05T21:15:36.513000 | Microsoft Windows LNK File UI Misrepresentation Remote Code Execution Vulnerabil | |
| CVE-2025-54988 | 9.8 | 0.03% | 2 | 1 | 2025-11-05T20:40:58 | Critical XXE in Apache Tika (tika-parser-pdf-module) in Apache Tika 1.13 through | |
| CVE-2025-20303 | 5.4 | 0.04% | 2 | 0 | 2025-11-05T17:48:33 | Multiple vulnerabilities in the web-based management interface of Cisco ISE and | |
| CVE-2025-8489 | 9.8 | 0.13% | 8 | 0 | 2025-11-04T15:41:31.450000 | The King Addons for Elementor – Free Elements, Widgets, Templates, and Features | |
| CVE-2021-44228 | 10.0 | 94.36% | 2 | 100 | template | 2025-10-27T17:40:33.680000 | Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12 |
| CVE-2025-61882 | 9.8 | 74.07% | 3 | 13 | template | 2025-10-27T17:08:52.230000 | Vulnerability in the Oracle Concurrent Processing product of Oracle E-Business S |
| CVE-2024-1086 | 7.8 | 86.39% | 1 | 9 | 2025-10-27T17:06:37.437000 | A use-after-free vulnerability in the Linux kernel's netfilter: nf_tables compon | |
| CVE-2025-57848 | 5.2 | 0.01% | 1 | 0 | 2025-10-27T13:20:15.637000 | A container privilege escalation flaw was found in certain Container-native Virt | |
| CVE-2025-10156 | 9.8 | 0.27% | 3 | 0 | 2025-10-02T19:04:56 | An Improper Handling of Exceptional Conditions vulnerability in the ZIP archive | |
| CVE-2025-10155 | 7.8 | 0.17% | 3 | 0 | 2025-09-18T12:51:23 | ### Summary Picklescan can be bypassed, allowing the detection of malicious pick | |
| CVE-2025-5518 | 6.5 | 0.04% | 4 | 86 | 2025-09-16T12:49:16.060000 | Authorization Bypass Through User-Controlled Key vulnerability with user privile | |
| CVE-2024-4367 | 8.8 | 32.60% | 2 | 24 | 2025-04-24T21:41:24 | ### Impact If pdf.js is used to load a malicious PDF, and PDF.js is configured w | |
| CVE-2021-21225 | 8.8 | 1.01% | 2 | 0 | 2024-11-21T05:47:48.830000 | Out of bounds memory access in V8 in Google Chrome prior to 90.0.4430.85 allowed | |
| CVE-2019-8457 | None | 27.14% | 2 | 0 | 2023-01-28T05:05:39 | SQLite3 from 3.6.0 to and including 3.27.2 is vulnerable to heap out-of-bound re | |
| CVE-2025-61260 | 0 | 0.00% | 4 | 0 | N/A | ||
| CVE-2025-66489 | 0 | 0.08% | 1 | 0 | N/A | ||
| CVE-2025-48633 | 0 | 0.00% | 6 | 1 | N/A | ||
| CVE-2025-48572 | 0 | 0.00% | 6 | 0 | N/A |
updated 2025-12-05T22:15:49.383000
2 posts
updated 2025-12-05T22:15:49.163000
2 posts
ZSPACE
https://www.cve.org/CVERecord?id=CVE-2025-14106
https://www.cve.org/CVERecord?id=CVE-2025-14107
TOZED
##ZSPACE
https://www.cve.org/CVERecord?id=CVE-2025-14106
https://www.cve.org/CVERecord?id=CVE-2025-14107
TOZED
##updated 2025-12-05T22:15:48.950000
2 posts
ZSPACE
https://www.cve.org/CVERecord?id=CVE-2025-14106
https://www.cve.org/CVERecord?id=CVE-2025-14107
TOZED
##ZSPACE
https://www.cve.org/CVERecord?id=CVE-2025-14106
https://www.cve.org/CVERecord?id=CVE-2025-14107
TOZED
##updated 2025-12-05T21:31:28
2 posts
Apache HTTP Server 2.4.66 was released yesterday, patching these sev:LOW and sev:MED vulns:
https://www.cve.org/CVERecord?id=CVE-2025-58098
https://www.cve.org/CVERecord?id=CVE-2025-59775
https://www.cve.org/CVERecord?id=CVE-2025-65082
##Apache HTTP Server 2.4.66 was released yesterday, patching these sev:LOW and sev:MED vulns:
https://www.cve.org/CVERecord?id=CVE-2025-58098
https://www.cve.org/CVERecord?id=CVE-2025-59775
https://www.cve.org/CVERecord?id=CVE-2025-65082
##updated 2025-12-05T21:31:27
2 posts
Apache HTTP Server 2.4.66 was released yesterday, patching these sev:LOW and sev:MED vulns:
https://www.cve.org/CVERecord?id=CVE-2025-58098
https://www.cve.org/CVERecord?id=CVE-2025-59775
https://www.cve.org/CVERecord?id=CVE-2025-65082
##Apache HTTP Server 2.4.66 was released yesterday, patching these sev:LOW and sev:MED vulns:
https://www.cve.org/CVERecord?id=CVE-2025-58098
https://www.cve.org/CVERecord?id=CVE-2025-59775
https://www.cve.org/CVERecord?id=CVE-2025-65082
##updated 2025-12-05T21:15:53.120000
2 posts
ZSPACE
https://www.cve.org/CVERecord?id=CVE-2025-14106
https://www.cve.org/CVERecord?id=CVE-2025-14107
TOZED
##ZSPACE
https://www.cve.org/CVERecord?id=CVE-2025-14106
https://www.cve.org/CVERecord?id=CVE-2025-14107
TOZED
##updated 2025-12-05T20:15:57.703000
2 posts
Apache HTTP Server 2.4.66 was released yesterday, patching these sev:LOW and sev:MED vulns:
https://www.cve.org/CVERecord?id=CVE-2025-58098
https://www.cve.org/CVERecord?id=CVE-2025-59775
https://www.cve.org/CVERecord?id=CVE-2025-65082
##Apache HTTP Server 2.4.66 was released yesterday, patching these sev:LOW and sev:MED vulns:
https://www.cve.org/CVERecord?id=CVE-2025-58098
https://www.cve.org/CVERecord?id=CVE-2025-59775
https://www.cve.org/CVERecord?id=CVE-2025-65082
##updated 2025-12-05T20:15:55.390000
2 posts
I love seeing default creds in a CVE.
https://www.cve.org/CVERecord?id=CVE-2025-53963
##An issue was discovered on Thermo Fisher Ion Torrent OneTouch 2 INS1005527 devices. They run an SSH server accessible over the default port 22. The root account has a weak default password of ionadmin, and a password change policy for the root account is not enforced. Thus, an attacker with network connectivity can achieve root code execution. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
I love seeing default creds in a CVE.
https://www.cve.org/CVERecord?id=CVE-2025-53963
##An issue was discovered on Thermo Fisher Ion Torrent OneTouch 2 INS1005527 devices. They run an SSH server accessible over the default port 22. The root account has a weak default password of ionadmin, and a password change policy for the root account is not enforced. Thus, an attacker with network connectivity can achieve root code execution. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
updated 2025-12-05T19:15:53.293000
2 posts
EITW vuln in ArrayOS. Advisory was published Wednesday and updated today, along with the CVE being published, so IDK if it was 0day or quickly exploited after the advisory.
https://www.jpcert.or.jp/at/2025/at250024.html
The DesktopDirect feature of the Array AG series provided by Array Networks contains a command injection vulnerability. If this vulnerability is exploited, an attacker may execute an arbitrary command. At the time of publication of this information, the CVE number for this vulnerability has not been numbered.
Not sure if this is something @Dio9sys and @da_667 are interested in.
Edit to add the CVE number since the description said it isn't available yet: CVE-2025-66644
##EITW vuln in ArrayOS. Advisory was published Wednesday and updated today, along with the CVE being published, so IDK if it was 0day or quickly exploited after the advisory.
https://www.jpcert.or.jp/at/2025/at250024.html
The DesktopDirect feature of the Array AG series provided by Array Networks contains a command injection vulnerability. If this vulnerability is exploited, an attacker may execute an arbitrary command. At the time of publication of this information, the CVE number for this vulnerability has not been numbered.
Not sure if this is something @Dio9sys and @da_667 are interested in.
Edit to add the CVE number since the description said it isn't available yet: CVE-2025-66644
##updated 2025-12-05T18:59:02
2 posts
1 repos
../ in laravel-file-manager.
##../ in laravel-file-manager.
##updated 2025-12-05T18:57:11.903000
1 posts
CVE-2025-66399 - SNMP Command Injection leads to RCE in Cacti https://cvefeed.io/vuln/detail/CVE-2025-66399
##updated 2025-12-05T18:56:23.270000
1 posts
CVE-2025-65955 - ImageMagick has a use-after-free/double-free risk in Options::fontFamily when clearing family https://cvefeed.io/vuln/detail/CVE-2025-65955
##updated 2025-12-05T18:41:56.647000
1 posts
CVE-2025-13354 - Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI <= 3.40.1 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Taxonomy Term Manipulation https://cvefeed.io/vuln/detail/CVE-2025-13354
##updated 2025-12-05T18:37:12.593000
1 posts
CVE-2025-13359 - Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI <= 3.40.1 - Authenticated (Contributor+) SQL Injection https://cvefeed.io/vuln/detail/CVE-2025-13359
##updated 2025-12-05T18:32:14
2 posts
Apache HTTP Server 2.4.66 was released yesterday, patching these sev:LOW and sev:MED vulns:
https://www.cve.org/CVERecord?id=CVE-2025-58098
https://www.cve.org/CVERecord?id=CVE-2025-59775
https://www.cve.org/CVERecord?id=CVE-2025-65082
##Apache HTTP Server 2.4.66 was released yesterday, patching these sev:LOW and sev:MED vulns:
https://www.cve.org/CVERecord?id=CVE-2025-58098
https://www.cve.org/CVERecord?id=CVE-2025-59775
https://www.cve.org/CVERecord?id=CVE-2025-65082
##updated 2025-12-05T18:15:57.067000
2 posts
Apache HTTP Server 2.4.66 was released yesterday, patching these sev:LOW and sev:MED vulns:
https://www.cve.org/CVERecord?id=CVE-2025-58098
https://www.cve.org/CVERecord?id=CVE-2025-59775
https://www.cve.org/CVERecord?id=CVE-2025-65082
##Apache HTTP Server 2.4.66 was released yesterday, patching these sev:LOW and sev:MED vulns:
https://www.cve.org/CVERecord?id=CVE-2025-58098
https://www.cve.org/CVERecord?id=CVE-2025-59775
https://www.cve.org/CVERecord?id=CVE-2025-65082
##updated 2025-12-05T17:44:58.770000
144 posts
100 repos
https://github.com/clevernyyyy/CVE-2025-55182-Dockerized
https://github.com/emadshanab/POC-for-CVE-2025-55182
https://github.com/alexandre-briongos-wavestone/react-cve-2025-55182-lab
https://github.com/Chocapikk/CVE-2025-55182
https://github.com/ZemarKhos/CVE-2025-55182-Exploit-PoC-Scanner
https://github.com/atastycookie/CVE-2025-55182
https://github.com/ducducuc111/CVE-2025-55182-poc
https://github.com/Chelsea486MHz/CVE-2025-55182-test
https://github.com/BankkRoll/Quickcheck-CVE-2025-55182-React-and-CVE-2025-66478-Next.js
https://github.com/ps-interactive/cve-2025-55182
https://github.com/Airis101/CVE-2025-55182-analysis
https://github.com/Ashwesker/Blackash-CVE-2025-55182
https://github.com/c0rydoras/CVE-2025-55182
https://github.com/hoosin/CVE-2025-55182
https://github.com/im-hanzou/CVE-2025-55182-POC-SCANNER
https://github.com/nehkark/CVE-2025-55182
https://github.com/Rat5ak/CVE-2025-55182-React2Shell-RCE-POC
https://github.com/Sotatek-KhaiNguyen3/CVE-2025-55182
https://github.com/assetnote/react2shell-scanner
https://github.com/SoICT-BKSEC/CVE-2025-55182-docker-lab
https://github.com/GarethMSheldon/React2Shell-CVE-2025-55182-Detector
https://github.com/younesZdDz/CVE-2025-55182
https://github.com/Rsatan/CVE-2025-55182-Tools
https://github.com/heiheishushu/rsc_detect_CVE-2025-55182
https://github.com/lachlan2k/React2Shell-CVE-2025-55182-original-poc
https://github.com/ngvcanh/CVE-2025-55182-Attack-Analysis
https://github.com/sudo-Yangziran/CVE-2025-55182POC
https://github.com/zessu/CVE-2025-55182-Typescript
https://github.com/sherlocksecurity/CVE-2025-55182-Exploit-scanner
https://github.com/Pa2sw0rd/exploit-CVE-2025-55182-poc
https://github.com/ceortiz33/CVE-2025-55182
https://github.com/selectarget/CVE-2025-55182-Exploit
https://github.com/hzhsec/cve_2025_55182_test
https://github.com/ZihxS/check-react-rce-cve-2025-55182
https://github.com/nomorebreach/POC-CVE-2025-55182
https://github.com/whiteov3rflow/CVE-2025-55182-poc
https://github.com/Spritualkb/CVE-2025-55182-exp
https://github.com/f0xyx/CVE-2025-55182-Scanner
https://github.com/freeqaz/react2shell
https://github.com/santihabib/CVE-2025-55182-analysis
https://github.com/NathanJ60/react2shell-interactive
https://github.com/aliclub0x00/CVE-2025-55182-POC-NEXTJS
https://github.com/XiaomingX/CVE-2025-55182-poc
https://github.com/EynaExp/CVE-2025-55182-POC
https://github.com/ejpir/CVE-2025-55182-research
https://github.com/jf0x3a/CVE-2025-55182-exploit
https://github.com/prestonhashworth/cve-2025-55182
https://github.com/nanwinata/CVE-2025-55182-Scanner
https://github.com/oways/React2shell-CVE-2025-55182-checker
https://github.com/hualy13/CVE-2025-55182
https://github.com/aquinn-r7/CVE-2025-55182-VulnCheckPOC
https://github.com/GelukCrab/React-Server-Components-RCE
https://github.com/nerium-security/CVE-2025-55182
https://github.com/ThemeHackers/CVE-2025-55182
https://github.com/logesh-GIT001/CVE-2025-55182
https://github.com/l4rm4nd/CVE-2025-55182
https://github.com/xkillbit/cve-2025-55182-scanner
https://github.com/joshterrill/CVE-2025-55182-realistic-poc
https://github.com/ABCFabian/React2Shell-CVE-2025-55182-Testing-Environment
https://github.com/fatguru/CVE-2025-55182-scanner
https://github.com/RuoJi6/CVE-2025-55182-RCE-shell
https://github.com/Darker-Ink/react-ssr-vulnerability
https://github.com/carlosaruy/CVE-2025-55182
https://github.com/tlfyyds/cve-2025-55182-getshell
https://github.com/topstar88/CVE-2025-55182
https://github.com/mingyisecurity-lab/CVE-2025-55182-TOOLS
https://github.com/dissy123/cve-2025-55182
https://github.com/RajChowdhury240/React2Shell-CVE-2025-55182
https://github.com/acheong08/CVE-2025-55182-poc
https://github.com/alsaut1/react2shell-lab
https://github.com/mrknow001/RSC_Detector
https://github.com/aspen-labs/CVE-2025-55182-checker
https://github.com/shamo0/react2shell-PoC
https://github.com/MedusaSH/POC-CVE-2025-55182
https://github.com/dwisiswant0/CVE-2025-55182
https://github.com/Cillian-Collins/CVE-2025-55182
https://github.com/0xPThree/cve-2025-55182
https://github.com/m3m0ryc0rrupt/CVE-2025-55182-PoC
https://github.com/ivaavimusic/React19-fix-vibecoders
https://github.com/jctommasi/react2shellVulnApp
https://github.com/sickwell/CVE-2025-55182
https://github.com/MrR0b0t19/CVE-2025-55182-shellinteractive
https://github.com/Atlantis02-sec/Vulnerability-assessment
https://github.com/rl0x01/CVE-2025-55182_PoC
https://github.com/kk12-30/CVE-2025-55182
https://github.com/sh1ro8/react2shell
https://github.com/pyroxenites/Nextjs_RCE_Exploit_Tool
https://github.com/Golden-Secure/CVE-2025-55182
https://github.com/Saturate/CVE-2025-55182-Scanner
https://github.com/zzhorc/CVE-2025-55182
https://github.com/Cr4at0r/Next.js-RCE-Scanner-BurpSuite-Extension-
https://github.com/CymulateResearch/React2Shell-Scanner
https://github.com/tobiasGuta/Next.js-RSC-RCE-Scanner-Burp-Suite-Extension
https://github.com/msanft/CVE-2025-55182
https://github.com/TH-SecForge/CVE-2025-55182
https://github.com/songsanggggg/CVE-2025-55182
https://github.com/onlylovetx/CVE-2025-55182-CVE-2025-66478-Exploit-GUI
https://github.com/pax-k/react2shell-CVE-2025-55182-full-rce-script
🚨 CVE-2025-55182: Meta React Server Components Remote Code Execution Vulnerability has been added to the CISA KEV Catalog
Added: 2025-12-05
Vendor: Meta
Product: React Server Components
CVSS: 10
CISA KEV Catalog: https://darkwebinformer.com/cisa-kev-catalog/
Write-up: https://www.vulncheck.com/blog/cve-2025-55182-react-nextjs
##Ooh @censys bringing the deets from the other perspective! https://censys.com/advisory/cve-2025-55182
##Explanation and full RCE PoC for CVE-2025-55182 https://github.com/msanft/CVE-2025-55182
##New. Suffer the buffer.
The issue "was triggered by changes being made to our body parsing logic while attempting to detect and mitigate an industry-wide vulnerability disclosed this week in React Server Components."
"As part of our ongoing work to protect customers using React against a critical vulnerability, CVE-2025-55182, we started rolling out an increase to our buffer size to 1MB, the default limit allowed by Next.js applications."
Cloudflare: outage on December 5, 2025 https://blog.cloudflare.com/5-december-2025-outage/ @cloudflare #Cloudflare #infosec #React
##🚨 [CISA-2025:1205] CISA Adds One Known Exploited Vulnerability to Catalog (https://secdb.nttzen.cloud/security-advisory/detail/CISA-2025:1205)
CISA has added one new vulnerability to its Known Exploited Vulnerabilities Catalog, based on evidence of active exploitation. These types of vulnerabilities are a frequent attack vector for malicious cyber actors and pose significant risk to the federal enterprise.
⚠️ CVE-2025-55182 (https://secdb.nttzen.cloud/cve/detail/CVE-2025-55182)
- Name: Meta React Server Components Remote Code Execution Vulnerability
- Action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- Known To Be Used in Ransomware Campaigns? Unknown
- Vendor: Meta
- Product: React Server Components
- Notes: https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components ; https://nvd.nist.gov/vuln/detail/CVE-2025-55182
#SecDB #InfoSec #CVE #CISA_KEV #cisa_20251205 #cisa20251205 #cve_2025_55182 #cve202555182
##New.
GreyNoise: CVE-2025-55182 (React2Shell) Opportunistic Exploitation In The Wild: What The GreyNoise Observation Grid Is Seeing So Far https://www.greynoise.io/blog/cve-2025-55182-react2shell-opportunistic-exploitation-in-the-wild-what-the-greynoise-observation-grid-is-seeing-so-far @greynoise #infosec #React #threatresearch
##CISA has updated the KEV catalogue.
CVE-2025-55182: Meta React Server Components Remote Code Execution Vulnerability https://www.cve.org/CVERecord?id=CVE-2025-55182
From yesterday:
CISA Launches New Platform to Strengthen Industry Engagement and Collaboration https://www.cisa.gov/news-events/news/cisa-launches-new-platform-strengthen-industry-engagement-and-collaboration #CISA #infosec #Meta #React #vulnerability
##Broadcom has two advisories today, one critical, one medium. You'll need a login for details https://support.broadcom.com/web/ecx/security-advisory
Broadcom Mainframe Software Security Advisory for Critical React RCE Vulnerability CVE-2025-55182, and ACF2 for z/OS 16.0 Vulnerability #infosec #Broadcom ##React
##Critical React2Shell Vulnerability Sparks Global Cybersecurity Alert
A newly discovered vulnerability in React and Next.js applications, known as React2Shell (CVE-2025-55182), is raising alarm across the cybersecurity community. This critical flaw allows remote JavaScript code execution, putting web applications and their users at serious risk. While patches have been released, proof-of-concept (POC) exploits are circulating widely, fueling a surge of attacks from…
https://undercodenews.com/critical-react2shell-vulnerability-sparks-global-cybersecurity-alert/
##Chinese hackers exploiting React2Shell bug impacting countless websites, Amazon researchers say
The bug, tagged as CVE-2025-55182 and referred to colloquially as React2Shell, was reported to Meta by researcher Lachlan Davidson on November 29...
🔗️ [Therecord] https://link.is.it/K0uf5R
##No surprise: We do see active hits of the React Vulnerability (CVE-2025-55182) against our honeypots.
The initial exploit attempts we are seeing originate from the following two IP addresses: 193.142.147.209 and 95.214.52.170. The payloads are either "ping -c 1 45.157.233.80" or "console.log('CVE-2025-55182-VULN')"
If you find an unpatched React app in your environment, you should assume that it has been compromised at this point. Also be careful with apps that may have pinned older versions fo React/Next.js
##React2Shell: Critical Remote Code Execution Threat Hits Reactjs and Nextjs
React.js, the popular JavaScript library powering interactive user interfaces for millions of web applications, has been hit by a critical security vulnerability. Disclosed by researcher Lachlan Davidson on November 29, 2025, this flaw—tracked as CVE-2025-55182 and dubbed React2Shell—poses a severe risk to server-side implementations of React.js. With a maximum CVSS score of 10.0, the…
https://undercodenews.com/react2shell-critical-remote-code-execution-threat-hits-reactjs-and-nextjs/
##AWS, from yesterday: China-nexus cyber threat groups rapidly exploit React2Shell vulnerability (CVE-2025-55182) https://aws.amazon.com/blogs/security/china-nexus-cyber-threat-groups-rapidly-exploit-react2shell-vulnerability-cve-2025-55182/
More:
The Hacker News: Chinese Threat Actors Have Started Exploiting the Newly Disclosed React2Shell Vulnerability https://thehackernews.com/2025/12/chinese-hackers-have-started-exploiting.html @thehackernews #infosec #React
##Progress Sitefinity Next.js Renderer appears to be vulnerable to this React vuln. React2Shell? Is that what everyone is calling it?
##The PoC of #react2shell from the original author https://github.com/lachlan2k/React2Shell-CVE-2025-55182-original-poc/blob/main/01-submitted-poc.js
##Yesterday, after various bogus AI slopped "PoC"s, eventually a functional PoC for the React RCE emerged:
https://github.com/msanft/CVE-2025-55182
We now have a PoC from the reporter of the vulnerability as well:
https://github.com/lachlan2k/React2Shell-CVE-2025-55182-original-poc
📊 39% of cloud environments are vulnerable to React2Shell.
New data from Wiz indicates that nearly 40% of cloud environments contain instances vulnerable to CVE-2025-55182. Even more concerning? 44% of all cloud environments have publicly exposed Next.js instances.
The "secure by design" assumption is working against defenders right now.
✅ Detection is LIVE.
We have updated the Network Vulnerability Scanner in Pentest-Tools.com to help you validate this specific configuration immediately.
As shown in the attached video, you can go from "exposed" to "confirmed" in seconds:
1. Select the Network Scanner
2. Input CVE-2025-55182
3. Get definitive proof with Request/Response evidence
Don't rely on version checks when the exposure surface is this wide.
🔗 Run the detection: https://pentest-tools.com/network-vulnerability-scanning/network-security-scanner-online
📜 Vulnerability breakdown: https://pentest-tools.com/vulnerabilities-exploits/react-server-components-remote-code-execution_28260
📈 Data source: https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
#AppSec #ReactJS #CloudSecurity #React2Shell #InfoSec #VulnerabilityManagement #NextJS
##CVE ID: CVE-2025-55182
Vendor: Meta
Product: React Server Components
Date Added: 2025-12-05
Notes: https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components ; https://nvd.nist.gov/vuln/detail/CVE-2025-55182
CVE URL: https://nvd.nist.gov/vuln/detail/CVE-2025-55182
I had the [mis?]fortune of being awake just as attackers decided to slam the public internet with React2Shell exploits. GreyNoise had a tag up for it yesterday afternoon.
Full write-up of the initial spate of attacks:
www.greynoise.io/blo...
1/3
CVE-2025-55182 (React2Shell) O...
I had the [mis?]fortune of being awake just as attackers decided to slam the public internet with React2Shell exploits. GreyNoise had a tag up for it yesterday afternoon.
Full write-up of the initial spate of attacks:
https://www.greynoise.io/blog/cve-2025-55182-react2shell-opportunistic-exploitation-in-the-wild-what-the-greynoise-observation-grid-is-seeing-so-far
1/3
Wild
https://github.com/Rat5ak/CVE-2025-55182-React2Shell-RCE-POC
##React2Shell (CVE-2025-55182): Chinesische Hackergruppen greifen kritische React-Schwachstelle an
Wenige Stunden nach der Veröffentlichung der Schwachstelle CVE-2025-55182 am 3. Dezember 2025 registrierten Sicherheitsforscher von Amazon erste Angriffsversuche. Die unter dem Namen React2Shell bekannt gewordene Lücke erhielt die Höchstbewertung von 10.0 im CVSS-System und ermöglicht die Ausführung von Code ohne Authentifizierung.
https://www.all-about-security.de/react2shell-cve-2025-55182-chinesische-hackergruppen-greifen-kritische-react-schwachstelle-an/
React2Shell Vulnerability Exploited by China-Linked Threat Actors Within Hours
The cybersecurity world is on high alert after a critical vulnerability affecting React and Next.js frameworks, dubbed React2Shell, was publicly disclosed. This flaw, officially tracked as CVE-2025-55182, allows remote execution of JavaScript code on servers without authentication. Alarmingly, multiple China-linked threat actors immediately began exploiting the vulnerability, highlighting…
##React2Shell critical flaw actively exploited in China-linked attacks
Multiple China-linked threat actors began exploiting the React2Shell vulnerability (CVE-2025-55182) affecting React and Next.js just hours after...
🔗️ [Bleepingcomputer] https://link.is.it/jllFod
##React2Shell CVE-2025-55182: Chinese Threat Groups Exploit Critical React Vulnerability Hours After Disclosure
Introduction Within hours of public disclosure, a critical vulnerability in React Server Components, dubbed React2Shell (CVE-2025-55182), has drawn the attention of state-linked threat actors. Rated with a maximum CVSS score of 10.0, the flaw enables unauthenticated remote code execution in React 19.x and Next.js 15.x/16.x environments. The rapid exploitation…
##the real React 10.0 CVE proof of concept (not the "AI" proof of slop)
https://github.com/lachlan2k/React2Shell-CVE-2025-55182-original-poc
##🎅 🌲 💫
Weihnachtlich erstrahlen Gassen
Auf zum Einkauf hasten Massen
Drinnen leuchten Kerzen hell
Nur Systemadministratoren
Lauschen bang dem Netz-Rumoren
Horch! Es naht #React2Shell!
⚠️ Alerte CERT-FR ⚠️
Le CERT-FR a connaissance de preuves de concept publiques pour la vulnérabilité CVE-2025-55182 affectant React Server Components et anticipe des exploitations en masse.
##Hm, das mit React2Shell wird noch etwas arg werden.
##Multiple threat groups are exploiting the critical React/Nex.js vulnerability
Active exploitation i underway for "React2Shell" (CVE-2025-55182), a critical CVSS 10.0 remote code execution vulnerability in React Server Components that allows attackers to abuse unsafe deserialization in the Flight protocol. Organizations must treat this as an emergency event and immediately update.
**THIS IS URGENT: If you're running server side React 19.x or Next.js 15.x/16.x (or frameworks using React Server Components like Waku or Redwood), attackers are already hacking your systems. Prioritize patching right now.**
#cybersecurity #infosec #attack #activeexploit
https://beyondmachines.net/event_details/multiple-threat-groups-are-exploiting-the-critical-react-nex-js-vulnerability-3-7-f-7-c/gD2P6Ple2L
Alleged (by Amazon) active exploitation of React Server Components (RSC) by Chinese threat actors. Has anyone else seen "real" exploitation attempts, not just running the fake PoCs that are out there?
##New Python Scanner Targets React Server Component Exposure in Nextjs Applications
A powerful new tool has emerged in the cybersecurity space, aimed at helping security teams detect exposed endpoints in modern ReactJS and Next.js applications. Named the CVE-2025-55182 Surface Scanner, this Python-based scanner provides a fast, non-intrusive method to identify potential security gaps in React Server Components (RSC) without performing full-blown exploits. With production…
##FML we have daft 10 IPs slinging the RSC/Next.js exploit along with one of the oddest JA4t hashes I've seen in a while.
someone(s) burned new infra to do so, too.
if any org gets compromised from an opportunistic campaign (like this) they fully deserve the ransomware/breach they get.
##Vulnerability Common Schema (replaces old CVE system)
{Product/module name or prefix}{severity number}{exploit type}
For example, CVE-2021-44228 becomes
Log4shell
CVE-2025-55182 becomes
React2shell
Simple.
##Cisco published a placeholder advisory for the React vuln CVE-2025-55182. They have not finished analyzing any of their products yet so impact has not been determined.
##Digital Supply Chain Risk: Critical Vulnerability Affecting React Allows for Unauthorized Remote Code Execution
CVE-2025-55182 (VulnDB ID: 428930), is a severe, unauthenticated RCE impacting a major component of React and its ecosystem.
🔗️ [Flashpoint] https://link.is.it/0tc98a
##To be clear, there are no public PoCs of yesterday's React vulnerability (CVE-2025-55182). The one that was being claimed as a POC has been outed as slop. Indeed, they even renamed the repo.
https://github.com/ejpir/CVE-2025-55182-research
The first PoCs for these vulns are now always fake.
Watch https://react2shell.com for disclosure from the discoverers.
##the bad news: lots of sloppity slop PoCs (slopocs???) abounding for the critical pre-auth React RCE
the good news: more time for you to patch your #React & #Nextjs apps ✨
my write up from yesterday on what to know & what to do: https://www.fastly.com/blog/fastlys-proactive-protection-critical-react-rce-cve-2025-55182
##Critical RCE vulnerability (React2shell) found in React Server Components and Next.js. Affects many modern web apps. Patch immediately or deploy WAF rules. Exploitation is imminent.
##Today in "AI ruins everything": AI generated "PoC" for the React RCE CVE-2025-55182, wasting countless defenders' hours, now get included in the CVE references. 🤦♂️
At least the co-author alongside the AI has updated the README now:
https://github.com/ejpir/CVE-2025-55182-poc
Looks like the original reporter plans on posting more details at some point in the future here:
https://react2shell.com/
Since I started to analyze #CVE-2025-55182 (#React, #NextJS #RCE) at work today, I decided to publish my analysis findings so far, given all the fuzz about the vulnerability: https://github.com/msanft/CVE-2025-55182
Feel free to contribute to the search for a proper RCE sink!
##@rotnroll666 Klar. Sonst hätte ich das hier nicht geschrieben. CVE-2025-55182
##🚨 CVE-2025-55182: CRITICAL React RCE risk for apps using a new feature. No patch yet; exploitation expected. Audit your React usage, enhance monitoring, and prep mitigations now. EU orgs at high risk! https://radar.offseq.com/threat/react2shell-in-the-wild-exploitation-expected-for--b4d27fa6 #OffSeq #ReactJS #RCE #Vulnerability
##@MoritzGlantz https://www.cve.org/CVERecord?id=CVE-2025-55182 React Server Gedöns
##⚠️ Critical RCE Vulnerabilities Discovered in React & Next.js | Wiz Blog
「 Wiz data indicates that 39% of cloud environments contain instances of Next.js or React in versions vulnerable to CVE-2025-55182 and/or CVE-2025-66478. Regarding Next.js, the framework itself is present in 69% of environments. Notably, 61% of those environments have public applications running Next.js, meaning that 44% of all cloud environments have publicly exposed Next.js instances 」
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
##Уязвимость в серверных компонентах React, позволяющая выполнить код на сервере
В серверных компонентах web-фреймворка React (RSC, React Server Components) устранена уязвимость (CVE-2025-55182), позволявшая через отправку запроса к серверному обработчику выполнить произвольный код на сервере. Уязвимости присвоен критический уровень опасности (10 из 10). Уязвимость проявляется в экспериментальных компонентах react-server-dom-webpack.....
Источник: https://www.opennet.ru/opennews/art.shtml?num=64373
Дата: Thu, 04 Dec 2025 11:12:04 +0300
Enjoy.
##📢 Faille critique RCE (CVSS 10) dans React Server Components (CVE-2025-55182) – mises à jour urgentes
📝 Selon react.dev, une vulnérabilité critique permettant une exécution de code à...
📖 cyberveille : https://cyberveille.ch/posts/2025-12-04-faille-critique-rce-cvss-10-dans-react-server-components-cve-2025-55182-mises-a-jour-urgentes/
🌐 source : https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
#CVE_2025_55182 #CVSS_10_0 #Cyberveille
📢 Next.js RSC : détection fiable d’une RCE (CVE-2025-55182 & CVE-2025-66478)
📝 Selon Searchlight Cyber (billet de recherche, 4 décembre 2025), une vulnérabilité de type RCE affectan...
📖 cyberveille : https://cyberveille.ch/posts/2025-12-04-next-js-rsc-detection-fiable-dune-rce-cve-2025-55182-cve-2025-66478/
🌐 source : https://slcyber.io/research-center/high-fidelity-detection-mechanism-for-rsc-next-js-rce-cve-2025-55182-cve-2025-66478/
#CVE_2025_55182_66478 #IOC #Cyberveille
Critical remote code execution vulnerabilities reported in React and Next.js
React and Next.js have patched two critical remote code execution vulnerabilities (CVE-2025-55182 and CVE-2025-66478) in React Server Components that allow unauthenticated attackers to execute arbitrary code through specially crafted HTTP requests exploiting insecure deserialization. Default configurations are vulnerable with near 100% exploitation reliability.
**If you're running React 19.x or Next.js 15.x/16.x (or frameworks using React Server Components like Waku or Redwood), attackers can take complete control of your servers with no authentication needed. Plan a VERY QUICK upgrade to the latest patched versions - this is the only fix available, so prioritize this update now.**
#cybersecurity #infosec #advisory #vulnerability
https://beyondmachines.net/event_details/critical-remote-code-execution-vulnerabilities-reported-in-react-and-next-js-j-3-6-0-d/gD2P6Ple2L
New Episode: SANS Stormcast Thursday, December 4th, 2025: CDN Headers; React Vulnerabiity; PickleScan Patch
Shownotes:
Attempts to Bypass CDNs
Our honeypots recently started receiving scans that included CDN specific headers.
https://isc.sans.edu/diary/Attempts%20to%20Bypass%20CDNs/32532
React Vulnerability CVE-2025-55182
React patched a critical
AntennaPod | Anytime Player | Apple Podcasts | Castamatic | CurioCaster | Fountain | gPodder | Overcast | Pocket Casts | Podcast Addict | Podcast Guru | Podnews | Podverse | Truefans
Or Listen right here.
##High Fidelity Detection Mechanism for RSC/Next.js RCE (CVE-2025-55182 & CVE-2025-66478) https://slcyber.io/research-center/high-fidelity-detection-mechanism-for-rsc-next-js-rce-cve-2025-55182-cve-2025-66478/
##Yikes. I always hate the damn red alert anxiety feeling I get when I read articles like the one linked. Its always that time between when something is publically disclosed, and when all packages and dependencies are patched an upgraded when likelihood of attack is highest, and obviously most possible. These two perfect 10/10 CVEs sure look like a doozy. No doubt hundreds of thousands of major things depend on these other major things, and likely hundreds of thousands of more things include them as dependencies or resource-wasting function packs, regardless of whether or not they are actually needed, and even some software puts these components in the chain, even when they're not actively being used.
And the exploit, with nearly 100% success-rate on all affected systems? A simple specially-crafted HTTP request.
https://www.aikido.dev/blog/react-nextjs-cve-2025-55182-rce
A maximum-severity vulnerability in React could enable remote code execution (RCE), and may affect more than a third of cloud service providers.
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
##A #criticalsecurityflaw (CVE-2025-55182) in #ReactServerComponents (#RSC) allows unauthenticated remote code execution. The vulnerability, impacting #React and #Nextjs, stems from unsafe payload processing and affects multiple versions of various packages. Users are advised to apply the available #patches immediately. https://thehackernews.com/2025/12/critical-rsc-bugs-in-react-and-nextjs.html?eicker.news #tech #media #news
##Ouch...
##⚠️ CRITICAL RCE in React Server Components & Next.js (CVE-2025-55182, CVSS 10.0): Unauthenticated attackers can execute code via unsafe deserialization. Patch React & Next.js now! Details: https://radar.offseq.com/threat/critical-rsc-bugs-in-react-and-nextjs-allow-unauth-4e911b0c #OffSeq #ReactJS #NextJS #RCE #InfoSec
##CVE-2025-66478: RCE in React Server Components
Bulletin ID: AWS-2025-030 Scope: AWS Content Type: Important (requires attention) Publication Date: 2025/12/03 20:00 PM PST
Description:
AWS is aware of the recently disclosed CVE-2025-55182 which affects the React Server Flight...
https://aws.amazon.com/security/security-bulletins/rss/aws-2025-030/
##LoL. Yep, my first thought is that this new React vuln is going to generate a lot of IR business. I am going to hell.
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
##Happy Holidays Everyone!
##Critical RCE Vulnerabilities in React and Next.js https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
##A maximum-severity security flaw has been disclosed in React Server Components (RSC) that, if successfully exploited, could result in remote code execution.
The vulnerability, tracked as CVE-2025-55182, carries a CVSS score of 10.0.
The vulnerability impacts versions 19.0, 19.1.0, 19.1.1, and 19.2.0 of the following npm packages -
It's worth noting that the vulnerability also affects Next.js using App Router. The issue has been assigned the CVE identifier CVE-2025-66478 (CVSS score: 10.0). It impacts versions >=14.3.0-canary.77, >=15, and >=16. Patched versions are 16.0.7, 15.5.7, 15.4.8, 15.3.6, 15.2.6, 15.1.9, and 15.0.5.
https://thehackernews.com/2025/12/critical-rsc-bugs-in-react-and-nextjs.html
#REACTjs #NEXTjs #infosec #cybersecurity #CVE202566478 #CVE202555182 #ShitIsOnFireYo
##As vulnerabilities go, a 10 is as bad as it gets. If you use #React or one of its derivatives (e.g., #Nextjs) you should upgrade Right. Now.
##“A pre-authentication remote code execution vulnerability exists in React Server Components versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 including the following packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. The vulnerable code unsafely deserializes payloads from HTTP requests to Server Function endpoints.“
##There is currently an incident at work due to the remote code execution vulnerability in React (see CVE-2025-55182).
Co-worker: How long will it take to patch the dev server UI?
Me: It's not affected.
Co-worker: How can it not be affected if it uses React?
Me:
This seems bad:
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
https://www.aikido.dev/blog/react-nextjs-cve-2025-55182-rce
Right?
##Do you use react? If so, you might want to update. See https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
##Breaking news: 🚨 #React and Next.js are now less secure than a chocolate teapot! 🍫☕️ Apparently, if you remember how to run `createnextapp`, you might be seconds away from becoming a hacker's best friend. The solution? #Patch like your life depends on it! 🛠️💻
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182 #Nextjs #Security #Vulnerability #HackerNews #HackerNews #ngated
For interested folks, here’s the React PR that fixes CVE-2025-55182 affecting React Server Components (CVSS 10.0 Critical Severity): https://github.com/facebook/react/pull/35277
Blog post: https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
> Even if your app does not implement any React Server Function endpoints it may still be vulnerable if your app supports React Server Components.
##Critical RCE Vulnerabilities in React and Next.js
Link: https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
Discussion: https://news.ycombinator.com/item?id=46136067
Critical RCE Vulnerabilities in React and Next.js
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
#HackerNews #CriticalRCE #Vulnerabilities #React #Nextjs #Cybersecurity #Vulnerabilities #CVE-2025-55182
##New.
This relates to CVE-2025-55182 and CVE-2025-66478. Wiz: Critical Vulnerabilities in React and Next.js: everything you need to know https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182 @wiz #infosec #vulnerabilities #threatresearch
##Critical RCE Vulnerabilities in React and Next.js
Link: https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
Comments: https://news.ycombinator.com/item?id=46136067
RCE in React Server Components, impacting React and Next.js. I usually don't say this, but patch right freakin' now. The React CVE listing (CVE-2025-55182) is a perfect 10.
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
https://nextjs.org/blog/CVE-2025-66478
There is an unauthenticated remote code execution vulnerability in React Server Components by exploiting a flaw in how React decodes payloads sent to React Server Function endpoints. This vulnerability is tracked as CVE-2025-55182.
Even if your app does not implement any React Server Function endpoints it may still be vulnerable if your app supports React Server Components.
The vulnerability is present in versions 19.0, 19.1.0, 19.1.1, and 19.2.0 of:
- react-server-dom-webpack
- react-server-dom-parcel
- react-server-dom-turbopack
Some React frameworks and bundlers depended on, had peer dependencies for, or included the vulnerable React packages. The following React frameworks & bundlers are affected: next, react-router, waku, @parcel/rsc, @vitejs/plugin-rsc, and rwsdk.
source: https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
##Critical RCE Vulnerabilities in React and Next.js
Link: https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
Discussion: https://news.ycombinator.com/item?id=46136067
@Weld I see this blog post from them: https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
##Critical RCE Vulnerabilities in React and Next.js
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
#ycombinator
There is an unauthenticated remote code execution vulnerability in React Server Components.
Even if your app does not implement any React Server Function endpoints it may still be vulnerable if your app supports React Server Components.
If your app’s React code does not use a server, your app is not affected by this vulnerability.
CVE-2025-55182
Mastodon server not impacted btw.
https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
##Critical RCE Vulnerabilities in React and Next.js
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
##Critical RCE Vulnerabilities in React and Next.js - https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
##Oh Hell yeah. Perfect 10 in React Server Components. 🥳
https://www.facebook.com/security/advisories/cve-2025-55182
##A pre-authentication remote code execution vulnerability exists in React Server Components versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 including the following packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. The vulnerable code unsafely deserializes payloads from HTTP requests to Server Function endpoints.
"We did a number of refactors [...] This also fixes a critical security vulnerability." 👀
CVE-2025-55182, an RCE in React Server Components just landed:
https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
Enjoy your patching, and make sure to check your bundled frameworks and dependencies.
Here's the commit:
https://github.com/facebook/react/commit/7dc903cd29dac55efb4424853fd0442fef3a8700
🚨 CVE-2025-55182: Meta React Server Components Remote Code Execution Vulnerability has been added to the CISA KEV Catalog
Added: 2025-12-05
Vendor: Meta
Product: React Server Components
CVSS: 10
CISA KEV Catalog: https://darkwebinformer.com/cisa-kev-catalog/
Write-up: https://www.vulncheck.com/blog/cve-2025-55182-react-nextjs
##Ooh @censys bringing the deets from the other perspective! https://censys.com/advisory/cve-2025-55182
##New. Suffer the buffer.
The issue "was triggered by changes being made to our body parsing logic while attempting to detect and mitigate an industry-wide vulnerability disclosed this week in React Server Components."
"As part of our ongoing work to protect customers using React against a critical vulnerability, CVE-2025-55182, we started rolling out an increase to our buffer size to 1MB, the default limit allowed by Next.js applications."
Cloudflare: outage on December 5, 2025 https://blog.cloudflare.com/5-december-2025-outage/ @cloudflare #Cloudflare #infosec #React
##New.
GreyNoise: CVE-2025-55182 (React2Shell) Opportunistic Exploitation In The Wild: What The GreyNoise Observation Grid Is Seeing So Far https://www.greynoise.io/blog/cve-2025-55182-react2shell-opportunistic-exploitation-in-the-wild-what-the-greynoise-observation-grid-is-seeing-so-far @greynoise #infosec #React #threatresearch
##CISA has updated the KEV catalogue.
CVE-2025-55182: Meta React Server Components Remote Code Execution Vulnerability https://www.cve.org/CVERecord?id=CVE-2025-55182
From yesterday:
CISA Launches New Platform to Strengthen Industry Engagement and Collaboration https://www.cisa.gov/news-events/news/cisa-launches-new-platform-strengthen-industry-engagement-and-collaboration #CISA #infosec #Meta #React #vulnerability
##Broadcom has two advisories today, one critical, one medium. You'll need a login for details https://support.broadcom.com/web/ecx/security-advisory
Broadcom Mainframe Software Security Advisory for Critical React RCE Vulnerability CVE-2025-55182, and ACF2 for z/OS 16.0 Vulnerability #infosec #Broadcom ##React
##Chinese hackers exploiting React2Shell bug impacting countless websites, Amazon researchers say
The bug, tagged as CVE-2025-55182 and referred to colloquially as React2Shell, was reported to Meta by researcher Lachlan Davidson on November 29...
🔗️ [Therecord] https://link.is.it/K0uf5R
##No surprise: We do see active hits of the React Vulnerability (CVE-2025-55182) against our honeypots.
The initial exploit attempts we are seeing originate from the following two IP addresses: 193.142.147.209 and 95.214.52.170. The payloads are either "ping -c 1 45.157.233.80" or "console.log('CVE-2025-55182-VULN')"
If you find an unpatched React app in your environment, you should assume that it has been compromised at this point. Also be careful with apps that may have pinned older versions fo React/Next.js
##AWS, from yesterday: China-nexus cyber threat groups rapidly exploit React2Shell vulnerability (CVE-2025-55182) https://aws.amazon.com/blogs/security/china-nexus-cyber-threat-groups-rapidly-exploit-react2shell-vulnerability-cve-2025-55182/
More:
The Hacker News: Chinese Threat Actors Have Started Exploiting the Newly Disclosed React2Shell Vulnerability https://thehackernews.com/2025/12/chinese-hackers-have-started-exploiting.html @thehackernews #infosec #React
##Progress Sitefinity Next.js Renderer appears to be vulnerable to this React vuln. React2Shell? Is that what everyone is calling it?
##The PoC of #react2shell from the original author https://github.com/lachlan2k/React2Shell-CVE-2025-55182-original-poc/blob/main/01-submitted-poc.js
##Yesterday, after various bogus AI slopped "PoC"s, eventually a functional PoC for the React RCE emerged:
https://github.com/msanft/CVE-2025-55182
We now have a PoC from the reporter of the vulnerability as well:
https://github.com/lachlan2k/React2Shell-CVE-2025-55182-original-poc
📊 39% of cloud environments are vulnerable to React2Shell.
New data from Wiz indicates that nearly 40% of cloud environments contain instances vulnerable to CVE-2025-55182. Even more concerning? 44% of all cloud environments have publicly exposed Next.js instances.
The "secure by design" assumption is working against defenders right now.
✅ Detection is LIVE.
We have updated the Network Vulnerability Scanner in Pentest-Tools.com to help you validate this specific configuration immediately.
As shown in the attached video, you can go from "exposed" to "confirmed" in seconds:
1. Select the Network Scanner
2. Input CVE-2025-55182
3. Get definitive proof with Request/Response evidence
Don't rely on version checks when the exposure surface is this wide.
🔗 Run the detection: https://pentest-tools.com/network-vulnerability-scanning/network-security-scanner-online
📜 Vulnerability breakdown: https://pentest-tools.com/vulnerabilities-exploits/react-server-components-remote-code-execution_28260
📈 Data source: https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
#AppSec #ReactJS #CloudSecurity #React2Shell #InfoSec #VulnerabilityManagement #NextJS
##CVE ID: CVE-2025-55182
Vendor: Meta
Product: React Server Components
Date Added: 2025-12-05
Notes: https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components ; https://nvd.nist.gov/vuln/detail/CVE-2025-55182
CVE URL: https://nvd.nist.gov/vuln/detail/CVE-2025-55182
I had the [mis?]fortune of being awake just as attackers decided to slam the public internet with React2Shell exploits. GreyNoise had a tag up for it yesterday afternoon.
Full write-up of the initial spate of attacks:
https://www.greynoise.io/blog/cve-2025-55182-react2shell-opportunistic-exploitation-in-the-wild-what-the-greynoise-observation-grid-is-seeing-so-far
1/3
React2Shell critical flaw actively exploited in China-linked attacks
Multiple China-linked threat actors began exploiting the React2Shell vulnerability (CVE-2025-55182) affecting React and Next.js just hours after...
🔗️ [Bleepingcomputer] https://link.is.it/jllFod
##🎅 🌲 💫
Weihnachtlich erstrahlen Gassen
Auf zum Einkauf hasten Massen
Drinnen leuchten Kerzen hell
Nur Systemadministratoren
Lauschen bang dem Netz-Rumoren
Horch! Es naht #React2Shell!
⚠️ Alerte CERT-FR ⚠️
Le CERT-FR a connaissance de preuves de concept publiques pour la vulnérabilité CVE-2025-55182 affectant React Server Components et anticipe des exploitations en masse.
##Hm, das mit React2Shell wird noch etwas arg werden.
##Multiple threat groups are exploiting the critical React/Nex.js vulnerability
Active exploitation i underway for "React2Shell" (CVE-2025-55182), a critical CVSS 10.0 remote code execution vulnerability in React Server Components that allows attackers to abuse unsafe deserialization in the Flight protocol. Organizations must treat this as an emergency event and immediately update.
**THIS IS URGENT: If you're running server side React 19.x or Next.js 15.x/16.x (or frameworks using React Server Components like Waku or Redwood), attackers are already hacking your systems. Prioritize patching right now.**
#cybersecurity #infosec #attack #activeexploit
https://beyondmachines.net/event_details/multiple-threat-groups-are-exploiting-the-critical-react-nex-js-vulnerability-3-7-f-7-c/gD2P6Ple2L
Alleged (by Amazon) active exploitation of React Server Components (RSC) by Chinese threat actors. Has anyone else seen "real" exploitation attempts, not just running the fake PoCs that are out there?
##FML we have daft 10 IPs slinging the RSC/Next.js exploit along with one of the oddest JA4t hashes I've seen in a while.
someone(s) burned new infra to do so, too.
if any org gets compromised from an opportunistic campaign (like this) they fully deserve the ransomware/breach they get.
##Vulnerability Common Schema (replaces old CVE system)
{Product/module name or prefix}{severity number}{exploit type}
For example, CVE-2021-44228 becomes
Log4shell
CVE-2025-55182 becomes
React2shell
Simple.
##Cisco published a placeholder advisory for the React vuln CVE-2025-55182. They have not finished analyzing any of their products yet so impact has not been determined.
##Digital Supply Chain Risk: Critical Vulnerability Affecting React Allows for Unauthorized Remote Code Execution
CVE-2025-55182 (VulnDB ID: 428930), is a severe, unauthenticated RCE impacting a major component of React and its ecosystem.
🔗️ [Flashpoint] https://link.is.it/0tc98a
##To be clear, there are no public PoCs of yesterday's React vulnerability (CVE-2025-55182). The one that was being claimed as a POC has been outed as slop. Indeed, they even renamed the repo.
https://github.com/ejpir/CVE-2025-55182-research
The first PoCs for these vulns are now always fake.
Watch https://react2shell.com for disclosure from the discoverers.
##the bad news: lots of sloppity slop PoCs (slopocs???) abounding for the critical pre-auth React RCE
the good news: more time for you to patch your #React & #Nextjs apps ✨
my write up from yesterday on what to know & what to do: https://www.fastly.com/blog/fastlys-proactive-protection-critical-react-rce-cve-2025-55182
##Today in "AI ruins everything": AI generated "PoC" for the React RCE CVE-2025-55182, wasting countless defenders' hours, now get included in the CVE references. 🤦♂️
At least the co-author alongside the AI has updated the README now:
https://github.com/ejpir/CVE-2025-55182-poc
Looks like the original reporter plans on posting more details at some point in the future here:
https://react2shell.com/
Since I started to analyze #CVE-2025-55182 (#React, #NextJS #RCE) at work today, I decided to publish my analysis findings so far, given all the fuzz about the vulnerability: https://github.com/msanft/CVE-2025-55182
Feel free to contribute to the search for a proper RCE sink!
##@rotnroll666 Klar. Sonst hätte ich das hier nicht geschrieben. CVE-2025-55182
##@MoritzGlantz https://www.cve.org/CVERecord?id=CVE-2025-55182 React Server Gedöns
##⚠️ Critical RCE Vulnerabilities Discovered in React & Next.js | Wiz Blog
「 Wiz data indicates that 39% of cloud environments contain instances of Next.js or React in versions vulnerable to CVE-2025-55182 and/or CVE-2025-66478. Regarding Next.js, the framework itself is present in 69% of environments. Notably, 61% of those environments have public applications running Next.js, meaning that 44% of all cloud environments have publicly exposed Next.js instances 」
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
##📢 Next.js RSC : détection fiable d’une RCE (CVE-2025-55182 & CVE-2025-66478)
📝 Selon Searchlight Cyber (billet de recherche, 4 décembre 2025), une vulnérabilité de type RCE affectan...
📖 cyberveille : https://cyberveille.ch/posts/2025-12-04-next-js-rsc-detection-fiable-dune-rce-cve-2025-55182-cve-2025-66478/
🌐 source : https://slcyber.io/research-center/high-fidelity-detection-mechanism-for-rsc-next-js-rce-cve-2025-55182-cve-2025-66478/
#CVE_2025_55182_66478 #IOC #Cyberveille
📢 Faille critique RCE (CVSS 10) dans React Server Components (CVE-2025-55182) – mises à jour urgentes
📝 Selon react.dev, une vulnérabilité critique permettant une exécution de code à...
📖 cyberveille : https://cyberveille.ch/posts/2025-12-04-faille-critique-rce-cvss-10-dans-react-server-components-cve-2025-55182-mises-a-jour-urgentes/
🌐 source : https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
#CVE_2025_55182 #CVSS_10_0 #Cyberveille
Critical remote code execution vulnerabilities reported in React and Next.js
React and Next.js have patched two critical remote code execution vulnerabilities (CVE-2025-55182 and CVE-2025-66478) in React Server Components that allow unauthenticated attackers to execute arbitrary code through specially crafted HTTP requests exploiting insecure deserialization. Default configurations are vulnerable with near 100% exploitation reliability.
**If you're running React 19.x or Next.js 15.x/16.x (or frameworks using React Server Components like Waku or Redwood), attackers can take complete control of your servers with no authentication needed. Plan a VERY QUICK upgrade to the latest patched versions - this is the only fix available, so prioritize this update now.**
#cybersecurity #infosec #advisory #vulnerability
https://beyondmachines.net/event_details/critical-remote-code-execution-vulnerabilities-reported-in-react-and-next-js-j-3-6-0-d/gD2P6Ple2L
High Fidelity Detection Mechanism for RSC/Next.js RCE (CVE-2025-55182 & CVE-2025-66478) https://slcyber.io/research-center/high-fidelity-detection-mechanism-for-rsc-next-js-rce-cve-2025-55182-cve-2025-66478/
##Yikes. I always hate the damn red alert anxiety feeling I get when I read articles like the one linked. Its always that time between when something is publically disclosed, and when all packages and dependencies are patched an upgraded when likelihood of attack is highest, and obviously most possible. These two perfect 10/10 CVEs sure look like a doozy. No doubt hundreds of thousands of major things depend on these other major things, and likely hundreds of thousands of more things include them as dependencies or resource-wasting function packs, regardless of whether or not they are actually needed, and even some software puts these components in the chain, even when they're not actively being used.
And the exploit, with nearly 100% success-rate on all affected systems? A simple specially-crafted HTTP request.
https://www.aikido.dev/blog/react-nextjs-cve-2025-55182-rce
A maximum-severity vulnerability in React could enable remote code execution (RCE), and may affect more than a third of cloud service providers.
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
##A #criticalsecurityflaw (CVE-2025-55182) in #ReactServerComponents (#RSC) allows unauthenticated remote code execution. The vulnerability, impacting #React and #Nextjs, stems from unsafe payload processing and affects multiple versions of various packages. Users are advised to apply the available #patches immediately. https://thehackernews.com/2025/12/critical-rsc-bugs-in-react-and-nextjs.html?eicker.news #tech #media #news
##CVE-2025-66478: RCE in React Server Components
Bulletin ID: AWS-2025-030 Scope: AWS Content Type: Important (requires attention) Publication Date: 2025/12/03 20:00 PM PST
Description:
AWS is aware of the recently disclosed CVE-2025-55182 which affects the React Server Flight...
https://aws.amazon.com/security/security-bulletins/rss/aws-2025-030/
##Admins and defenders gird themselves against maximum-severity server vuln
“I usually don’t say this, but patch right freakin’ now,” one researcher wrote. “The React CVE listing (CVE-2025-55182)…
#NewsBeep #News #US #USA #UnitedStates #UnitedStatesOfAmerica #Technology
https://www.newsbeep.com/us/329246/
LoL. Yep, my first thought is that this new React vuln is going to generate a lot of IR business. I am going to hell.
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
##Critical RCE Vulnerabilities in React and Next.js https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
##A maximum-severity security flaw has been disclosed in React Server Components (RSC) that, if successfully exploited, could result in remote code execution.
The vulnerability, tracked as CVE-2025-55182, carries a CVSS score of 10.0.
The vulnerability impacts versions 19.0, 19.1.0, 19.1.1, and 19.2.0 of the following npm packages -
It's worth noting that the vulnerability also affects Next.js using App Router. The issue has been assigned the CVE identifier CVE-2025-66478 (CVSS score: 10.0). It impacts versions >=14.3.0-canary.77, >=15, and >=16. Patched versions are 16.0.7, 15.5.7, 15.4.8, 15.3.6, 15.2.6, 15.1.9, and 15.0.5.
https://thehackernews.com/2025/12/critical-rsc-bugs-in-react-and-nextjs.html
#REACTjs #NEXTjs #infosec #cybersecurity #CVE202566478 #CVE202555182 #ShitIsOnFireYo
##“A pre-authentication remote code execution vulnerability exists in React Server Components versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 including the following packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. The vulnerable code unsafely deserializes payloads from HTTP requests to Server Function endpoints.“
##There is currently an incident at work due to the remote code execution vulnerability in React (see CVE-2025-55182).
Co-worker: How long will it take to patch the dev server UI?
Me: It's not affected.
Co-worker: How can it not be affected if it uses React?
Me:
This seems bad:
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
https://www.aikido.dev/blog/react-nextjs-cve-2025-55182-rce
Right?
##For interested folks, here’s the React PR that fixes CVE-2025-55182 affecting React Server Components (CVSS 10.0 Critical Severity): https://github.com/facebook/react/pull/35277
Blog post: https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
> Even if your app does not implement any React Server Function endpoints it may still be vulnerable if your app supports React Server Components.
##Critical RCE Vulnerabilities in React and Next.js
Link: https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
Discussion: https://news.ycombinator.com/item?id=46136067
Critical RCE Vulnerabilities in React and Next.js
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
#HackerNews #CriticalRCE #Vulnerabilities #React #Nextjs #Cybersecurity #Vulnerabilities #CVE-2025-55182
##New.
This relates to CVE-2025-55182 and CVE-2025-66478. Wiz: Critical Vulnerabilities in React and Next.js: everything you need to know https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182 @wiz #infosec #vulnerabilities #threatresearch
##Critical RCE Vulnerabilities in React and Next.js
Link: https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
Comments: https://news.ycombinator.com/item?id=46136067
RCE in React Server Components, impacting React and Next.js. I usually don't say this, but patch right freakin' now. The React CVE listing (CVE-2025-55182) is a perfect 10.
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
https://nextjs.org/blog/CVE-2025-66478
There is an unauthenticated remote code execution vulnerability in React Server Components by exploiting a flaw in how React decodes payloads sent to React Server Function endpoints. This vulnerability is tracked as CVE-2025-55182.
Even if your app does not implement any React Server Function endpoints it may still be vulnerable if your app supports React Server Components.
The vulnerability is present in versions 19.0, 19.1.0, 19.1.1, and 19.2.0 of:
- react-server-dom-webpack
- react-server-dom-parcel
- react-server-dom-turbopack
Some React frameworks and bundlers depended on, had peer dependencies for, or included the vulnerable React packages. The following React frameworks & bundlers are affected: next, react-router, waku, @parcel/rsc, @vitejs/plugin-rsc, and rwsdk.
source: https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
##Critical RCE Vulnerabilities in React and Next.js
Link: https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
Discussion: https://news.ycombinator.com/item?id=46136067
@Weld I see this blog post from them: https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
##Critical RCE Vulnerabilities in React and Next.js
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
#ycombinator
There is an unauthenticated remote code execution vulnerability in React Server Components.
Even if your app does not implement any React Server Function endpoints it may still be vulnerable if your app supports React Server Components.
If your app’s React code does not use a server, your app is not affected by this vulnerability.
CVE-2025-55182
Mastodon server not impacted btw.
https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
##Critical RCE Vulnerabilities in React and Next.js
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
##Oh Hell yeah. Perfect 10 in React Server Components. 🥳
https://www.facebook.com/security/advisories/cve-2025-55182
##A pre-authentication remote code execution vulnerability exists in React Server Components versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 including the following packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. The vulnerable code unsafely deserializes payloads from HTTP requests to Server Function endpoints.
"We did a number of refactors [...] This also fixes a critical security vulnerability." 👀
CVE-2025-55182, an RCE in React Server Components just landed:
https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
Enjoy your patching, and make sure to check your bundled frameworks and dependencies.
Here's the commit:
https://github.com/facebook/react/commit/7dc903cd29dac55efb4424853fd0442fef3a8700
updated 2025-12-05T17:16:03.117000
2 posts
Hi, my name is cR0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000w
Hi, my name is cR0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000w
updated 2025-12-05T17:16:02.917000
2 posts
updated 2025-12-05T17:16:02.713000
2 posts
updated 2025-12-05T16:33:46.797000
1 posts
Two new advisories from Nvidia, both high severity:
- CVE-2025-33211 and CVE-2025-33201: NVIDIA Triton Inference Server https://nvidia.custhelp.com/app/answers/detail/a_id/5734
- CVE-2025-33208: NVIDIA TAO https://nvidia.custhelp.com/app/answers/detail/a_id/5730 #Nvidia #infosec #vulnerability
##updated 2025-12-05T16:15:50.773000
2 posts
Hardcoded JWT secret in something called GoAway. It appears to be a similar project to Pihole.
https://github.com/gian2dchris/CVEs/tree/CVE-2025-65730/CVE-2025-65730
##Hardcoded JWT secret in something called GoAway. It appears to be a similar project to Pihole.
https://github.com/gian2dchris/CVEs/tree/CVE-2025-65730/CVE-2025-65730
##updated 2025-12-05T16:15:49.540000
2 posts
updated 2025-12-05T15:37:59.973000
1 posts
🚨 CVE-2025-66222 (CRITICAL, CVSS 9.7): ThinkInAIXYZ deepchat <0.5.0 exposes stored XSS in Mermaid diagrams, leading to RCE via Electron IPC. Patch to 0.5.0+, restrict untrusted content, and monitor for abuse! https://radar.offseq.com/threat/cve-2025-66222-cwe-94-improper-control-of-generati-ddf80d66 #OffSeq #Vuln #AI #Security
##updated 2025-12-05T15:10:25.093000
1 posts
CVE-2025-13946 - Loop with Unreachable Exit Condition ('Infinite Loop') in Wireshark https://cvefeed.io/vuln/detail/CVE-2025-13946
##updated 2025-12-05T12:30:19
1 posts
⚠️ CVE-2025-13614: HIGH-severity stored XSS in wpkube Cool Tag Cloud plugin (all versions). Authenticated contributors can inject malicious JS via shortcode, risking credential theft & site compromise. Audit permissions & monitor usage. Details: https://radar.offseq.com/threat/cve-2025-13614-cwe-79-improper-neutralization-of-i-7f71da3c #OffSeq #WordPress #XSS
##updated 2025-12-05T07:16:11.350000
1 posts
🚨 CVE-2025-12850: HIGH severity SQL Injection in My auctions allegro WordPress plugin (all versions ≤3.6.32). Unauthenticated attackers can extract sensitive DB data. Patch when available, use WAF/input validation now. Details: https://radar.offseq.com/threat/cve-2025-12850-cwe-89-improper-neutralization-of-s-a9c55820 #OffSeq #WordPress #Vuln
##updated 2025-12-05T07:16:11.117000
1 posts
🔥 CRITICAL: CVE-2025-12374 in 'User Verification by PickPlugins' (WP, ≤2.0.39) allows auth bypass via empty OTP—admin takeover possible. Disable plugin or implement WAF rules until patched! https://radar.offseq.com/threat/cve-2025-12374-cwe-287-improper-authentication-in--8c3c4127 #OffSeq #WordPress #CVE202512374
##updated 2025-12-05T06:31:32
1 posts
🚨 CVE-2025-13066: HIGH severity vuln in kraftplugins Demo Importer Plus (all versions). Author+ users can upload dangerous files & trigger RCE. No patch yet—restrict access, monitor uploads, use WAFs. https://radar.offseq.com/threat/cve-2025-13066-cwe-434-unrestricted-upload-of-file-299ff291 #OffSeq #WordPress #Vuln #RCE
##updated 2025-12-05T06:31:30
1 posts
⚠️ CRITICAL: CVE-2025-13313 in dripadmin CRM Memberships (≤2.5) lets unauth attackers reset user passwords & harvest emails via unprotected AJAX endpoints. Restrict access, monitor for abuse, patch ASAP. Details: https://radar.offseq.com/threat/cve-2025-13313-cwe-862-missing-authorization-in-dr-61158105 #OffSeq #WordPress #ThreatIntel #CVE202513313
##updated 2025-12-05T00:31:11
2 posts
updated 2025-12-05T00:31:11
2 posts
WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##updated 2025-12-05T00:31:11
2 posts
WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##updated 2025-12-05T00:31:11
2 posts
WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##updated 2025-12-05T00:31:11
2 posts
WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##updated 2025-12-04T23:15:45.300000
2 posts
BRB, gonna put on some Tool.
https://access.redhat.com/security/cve/CVE-2024-3884
##A flaw was found in Undertow that can cause remote denial of service attacks. When the server uses the FormEncodedDataDefinition.doParse(StreamSourceChannel) method to parse large form data encoding with application/x-www-form-urlencoded, the method will cause an OutOfMemory issue. This flaw allows unauthorized users to cause a remote denial of service (DoS) attack.
BRB, gonna put on some Tool.
https://access.redhat.com/security/cve/CVE-2024-3884
##A flaw was found in Undertow that can cause remote denial of service attacks. When the server uses the FormEncodedDataDefinition.doParse(StreamSourceChannel) method to parse large form data encoding with application/x-www-form-urlencoded, the method will cause an OutOfMemory issue. This flaw allows unauthorized users to cause a remote denial of service (DoS) attack.
updated 2025-12-04T22:15:48.583000
2 posts
WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##updated 2025-12-04T22:15:48.290000
2 posts
WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##updated 2025-12-04T22:15:48.140000
2 posts
WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##updated 2025-12-04T22:15:48
2 posts
WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##updated 2025-12-04T22:15:47.863000
2 posts
WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##updated 2025-12-04T22:15:47.697000
2 posts
WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##updated 2025-12-04T22:15:47.520000
2 posts
WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##updated 2025-12-04T22:15:46.920000
2 posts
WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##WatchGuard
https://www.cve.org/CVERecord?id=CVE-2025-12026
https://www.cve.org/CVERecord?id=CVE-2025-12195
https://www.cve.org/CVERecord?id=CVE-2025-12196
https://www.cve.org/CVERecord?id=CVE-2025-11838
https://www.cve.org/CVERecord?id=CVE-2025-13936
https://www.cve.org/CVERecord?id=CVE-2025-13937
https://www.cve.org/CVERecord?id=CVE-2025-13938
https://www.cve.org/CVERecord?id=CVE-2025-13939
https://www.cve.org/CVERecord?id=CVE-2025-13940
https://www.cve.org/CVERecord?id=CVE-2025-1545
https://www.cve.org/CVERecord?id=CVE-2025-6946
https://www.cve.org/CVERecord?id=CVE-2025-1910
cc: @Dio9sys @da_667 but I didn't look to see if they were network vulns that you could write sigs for or not.
##updated 2025-12-04T21:31:17
1 posts
🚨 CVE-2025-66571: CRITICAL PHP object injection in UNA CMS 9.0.0-RC1–14.0.0-RC4. Remote, unauthenticated code execution via unsafe unserialize(). Restrict endpoints, monitor logs, & apply mitigations. Patch ASAP. https://radar.offseq.com/threat/cve-2025-66571-cwe-502-deserialization-of-untruste-c276a0d9 #OffSeq #CVE202566571 #Vuln
##updated 2025-12-04T21:31:12
2 posts
Genexis
https://www.cve.org/CVERecord?id=CVE-2025-65883
ALLNET
https://www.cve.org/CVERecord?id=CVE-2025-29268
##Genexis
https://www.cve.org/CVERecord?id=CVE-2025-65883
ALLNET
https://www.cve.org/CVERecord?id=CVE-2025-29268
##updated 2025-12-04T21:31:06
2 posts
Genexis
https://www.cve.org/CVERecord?id=CVE-2025-65883
ALLNET
https://www.cve.org/CVERecord?id=CVE-2025-29268
##Genexis
https://www.cve.org/CVERecord?id=CVE-2025-65883
ALLNET
https://www.cve.org/CVERecord?id=CVE-2025-29268
##updated 2025-12-04T21:31:06
2 posts
Genexis
https://www.cve.org/CVERecord?id=CVE-2025-65883
ALLNET
https://www.cve.org/CVERecord?id=CVE-2025-29268
##Genexis
https://www.cve.org/CVERecord?id=CVE-2025-65883
ALLNET
https://www.cve.org/CVERecord?id=CVE-2025-29268
##updated 2025-12-04T19:20:42.487000
1 posts
CVE-2025-13638 - Google Chrome Media Stream Use After Free Vulnerability https://cvefeed.io/vuln/detail/CVE-2025-13638
##updated 2025-12-04T18:31:01
2 posts
Akamai patches critical HTTP request smuggling flaw in Edge Server infrastructure
Akamai patched a critical HTTP Request Smuggling vulnerability (CVE-2025-66373) in its global edge server infrastructure that incorrectly processed malformed HTTP/1.1 chunked transfer encoding, potentially allowing attackers to bypass security controls, impersonate users, poison caches, and execute unauthorized requests.
**You can't do anything about this advisory. It's already fixed. But keep a record of it if you are using Akamai for vendor evaluation.**
#cybersecurity #infosec #advisory #vulnerability
https://beyondmachines.net/event_details/akamai-patches-critical-http-request-smuggling-flaw-in-edge-server-infrastructure-f-1-l-e-5/gD2P6Ple2L
Akamai patches critical HTTP request smuggling flaw in Edge Server infrastructure
Akamai patched a critical HTTP Request Smuggling vulnerability (CVE-2025-66373) in its global edge server infrastructure that incorrectly processed malformed HTTP/1.1 chunked transfer encoding, potentially allowing attackers to bypass security controls, impersonate users, poison caches, and execute unauthorized requests.
**You can't do anything about this advisory. It's already fixed. But keep a record of it if you are using Akamai for vendor evaluation.**
#cybersecurity #infosec #advisory #vulnerability
https://beyondmachines.net/event_details/akamai-patches-critical-http-request-smuggling-flaw-in-edge-server-infrastructure-f-1-l-e-5/gD2P6Ple2L
updated 2025-12-04T18:31:01
2 posts
https://access.redhat.com/security/cve/cve-2025-66287
##A flaw was found in WebKitGTK. Processing malicious web content can cause an unexpected process crash due to improper memory handling.
https://access.redhat.com/security/cve/cve-2025-66287
##A flaw was found in WebKitGTK. Processing malicious web content can cause an unexpected process crash due to improper memory handling.
updated 2025-12-04T18:06:43.940000
1 posts
CVE-2025-13720 - Google Chrome Heap Corruption Vulnerability https://cvefeed.io/vuln/detail/CVE-2025-13720
##updated 2025-12-04T17:15:57.120000
5 posts
Oh der Spaß geht weiter. D.h. die Java 8 Versionen sind auch mit entferntem PDF Modul angreifbar.
Apache Tika has XXE vulnerability · CVE-2025-66516 · GitHub Advisory Database · GitHub
https://github.com/advisories/GHSA-f58c-gq56-vjjf
🚨 CVE-2025-66516 CRITICAL: XXE in Apache Tika core (v1.13–3.2.1), tika-pdf-module, tika-parsers. Exploitable via crafted PDF XFA files — risks data exfil & DoS. Patch to 3.2.2+ now! https://radar.offseq.com/threat/cve-2025-66516-cwe-611-improper-restriction-of-xml-fa601313 #OffSeq #ApacheTika #XXE #Vuln
##Perfect 10 XXE in Apache Tika tika-core. 🥳
https://lists.apache.org/thread/s5x3k93nhbkqzztp1olxotoyjpdlps9k
##Critical XXE in Apache Tika tika-core (1.13-3.2.1), tika-pdf-module (2.0.0-3.2.1) and tika-parsers (1.13-1.28.5) modules on all platforms allows an attacker to carry out XML External Entity injection via a crafted XFA file inside of a PDF. \n\nThis CVE covers the same vulnerability as in CVE-2025-54988. However, this CVE expands the scope of affected packages in two ways. \n\nFirst, while the entrypoint for the vulnerability was the tika-parser-pdf-module as reported in CVE-2025-54988, the vulnerability and its fix were in tika-core. Users who upgraded the tika-parser-pdf-module but did not upgrade tika-core to >= 3.2.2 would still be vulnerable. \n\nSecond, the original report failed to mention that in the 1.x Tika releases, the PDFParser was in the \"org.apache.tika:tika-parsers\" module.
Oh der Spaß geht weiter. D.h. die Java 8 Versionen sind auch mit entferntem PDF Modul angreifbar.
Apache Tika has XXE vulnerability · CVE-2025-66516 · GitHub Advisory Database · GitHub
https://github.com/advisories/GHSA-f58c-gq56-vjjf
Perfect 10 XXE in Apache Tika tika-core. 🥳
https://lists.apache.org/thread/s5x3k93nhbkqzztp1olxotoyjpdlps9k
##Critical XXE in Apache Tika tika-core (1.13-3.2.1), tika-pdf-module (2.0.0-3.2.1) and tika-parsers (1.13-1.28.5) modules on all platforms allows an attacker to carry out XML External Entity injection via a crafted XFA file inside of a PDF. \n\nThis CVE covers the same vulnerability as in CVE-2025-54988. However, this CVE expands the scope of affected packages in two ways. \n\nFirst, while the entrypoint for the vulnerability was the tika-parser-pdf-module as reported in CVE-2025-54988, the vulnerability and its fix were in tika-core. Users who upgraded the tika-parser-pdf-module but did not upgrade tika-core to >= 3.2.2 would still be vulnerable. \n\nSecond, the original report failed to mention that in the 1.x Tika releases, the PDFParser was in the \"org.apache.tika:tika-parsers\" module.
updated 2025-12-04T17:15:08.283000
2 posts
libpng 1.6.0 through 1.6.51 out-of-bounds read vulnerability CVE-2025-66293 may lead to information disclosure (or denial of service). Due to a bug processing a PNG image may lead to read of 1012 bytes past the end of an array. Depending on the contents of the memory beyond this array, some confidential information may be leaked.
The conditions for the issue to trigger require the image to processed through the simplified API with an output format without alpha and no explicit background color. This means that not every application processing PNG images is leaking information. Also a limiting factor is that the affected system would need to return the decoded image data for the information leak to happen in the first place. Finally the information would need to cross a security context (for example from server to client, from privileged process to unprivileged or from user to another user) for the leak to have a security impact.
Interestingly the images resulting in the leak are in fact fully PNG spec compliant.
libpng 1.6.0 through 1.6.51 are affected. The vulnerability is fixed in libpng 1.6.52.
source: https://www.openwall.com/lists/oss-security/2025/12/03/5
##libpng 1.6.0 through 1.6.51 out-of-bounds read vulnerability CVE-2025-66293 may lead to information disclosure (or denial of service). Due to a bug processing a PNG image may lead to read of 1012 bytes past the end of an array. Depending on the contents of the memory beyond this array, some confidential information may be leaked.
The conditions for the issue to trigger require the image to processed through the simplified API with an output format without alpha and no explicit background color. This means that not every application processing PNG images is leaking information. Also a limiting factor is that the affected system would need to return the decoded image data for the information leak to happen in the first place. Finally the information would need to cross a security context (for example from server to client, from privileged process to unprivileged or from user to another user) for the leak to have a security impact.
Interestingly the images resulting in the leak are in fact fully PNG spec compliant.
libpng 1.6.0 through 1.6.51 are affected. The vulnerability is fixed in libpng 1.6.52.
source: https://www.openwall.com/lists/oss-security/2025/12/03/5
##updated 2025-12-04T17:15:08.283000
2 posts
1 repos
https://github.com/Ch1keen/CVE-2025-50360
##A heap buffer overflow in compiler.c and compiler.h in Pepper language 0.1.1commit 961a5d9988c5986d563310275adad3fd181b2bb7. Malicious execution of a pepper source file(.pr) could lead to arbitrary code execution or Denial of Service.
https://github.com/Ch1keen/CVE-2025-50360
##A heap buffer overflow in compiler.c and compiler.h in Pepper language 0.1.1commit 961a5d9988c5986d563310275adad3fd181b2bb7. Malicious execution of a pepper source file(.pr) could lead to arbitrary code execution or Denial of Service.
updated 2025-12-04T17:15:08.283000
2 posts
CVE-2025-13342 - Frontend Admin by DynamiApps <= 3.28.20 - Unauthenticated Arbitrary Options Update https://cvefeed.io/vuln/detail/CVE-2025-13342
##CVE-2025-13342 - Frontend Admin by DynamiApps <= 3.28.20 - Unauthenticated Arbitrary Options Update https://cvefeed.io/vuln/detail/CVE-2025-13342
##updated 2025-12-04T17:15:08.283000
1 posts
CVE-2025-13756 - Fluent Booking – The Ultimate Appointments Scheduling, Events Booking, Events Calendar Solution <= 1.9.11 - Authenticated (Subscriber+) Missing Authorization to Calendar Import and Management https://cvefeed.io/vuln/detail/CVE-2025-13756
##updated 2025-12-04T17:15:08.283000
1 posts
CVE-2025-13947 - Webkit: webkitgtk: remote user-assisted information disclosure via file drag-and-drop https://cvefeed.io/vuln/detail/CVE-2025-13947
##updated 2025-12-04T17:15:08.283000
1 posts
CVE-2025-29864 - ALZip SmartScreen Bypass Vulnerability https://cvefeed.io/vuln/detail/CVE-2025-29864
##updated 2025-12-04T17:15:08.283000
1 posts
CVE-2025-13472 - Missing authorization in BlazeMeter Jenkins Plugin https://cvefeed.io/vuln/detail/CVE-2025-13472
##updated 2025-12-04T17:15:08.283000
2 posts
5 repos
https://github.com/0xnemian/CVE-2025-13486.-CVE-2025-13486
https://github.com/lasthero-887/CVE-2025-13486---Poc
https://github.com/MataKucing-OFC/CVE-2025-13486
CVE-2025-13486 - Advanced Custom Fields: Extended 0.9.0.5 - 0.9.1.1 - Unauthenticated Remote Code Execution in prepare_form https://cvefeed.io/vuln/detail/CVE-2025-13486
##CVE-2025-13486 - Advanced Custom Fields: Extended 0.9.0.5 - 0.9.1.1 - Unauthenticated Remote Code Execution in prepare_form https://cvefeed.io/vuln/detail/CVE-2025-13486
##updated 2025-12-04T17:15:08.283000
1 posts
CVE-2025-12954 - Timetable and Event Schedule by MotoPress < 2.4.16 - Contributor+ Event Disclosure via IDOR https://cvefeed.io/vuln/detail/CVE-2025-12954
##updated 2025-12-04T17:15:08.283000
1 posts
1 repos
CVE-2025-12585 - MxChat – AI Chatbot for WordPress <= 2.5.5 - Unauthenticated Information Exposure https://cvefeed.io/vuln/detail/CVE-2025-12585
##updated 2025-12-04T17:15:08.283000
1 posts
CVE-2025-13646 - Modula 2.13.1 - 2.13.2 - Authenticated (Author+) Arbitrary File Upload via Race Condition https://cvefeed.io/vuln/detail/CVE-2025-13646
##updated 2025-12-04T17:15:08.283000
1 posts
CVE-2025-13448 - CSSIgniter Shortcodes <= 2.4.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'element' Shortcode Attribute https://cvefeed.io/vuln/detail/CVE-2025-13448
##updated 2025-12-04T17:15:08.283000
1 posts
CVE-2025-66476 - Vim for Windows Uncontrolled Search Path Element Remote Code Execution Vulnerability https://cvefeed.io/vuln/detail/CVE-2025-66476
##updated 2025-12-04T17:15:08.283000
2 posts
CVE-2025-64298 - Mirion Medical EC2 Software NMIS BioDose Incorrect Permission Assignment for Critical Resource https://cvefeed.io/vuln/detail/CVE-2025-64298
##CVE-2025-64298 - Mirion Medical EC2 Software NMIS BioDose Incorrect Permission Assignment for Critical Resource https://cvefeed.io/vuln/detail/CVE-2025-64298
##updated 2025-12-04T17:15:08.283000
2 posts
CVE-2025-62575 - Mirion Medical EC2 Software NMIS BioDose Incorrect Permission Assignment for Critical Resource https://cvefeed.io/vuln/detail/CVE-2025-62575
##CVE-2025-62575 - Mirion Medical EC2 Software NMIS BioDose Incorrect Permission Assignment for Critical Resource https://cvefeed.io/vuln/detail/CVE-2025-62575
##updated 2025-12-04T17:15:08.283000
1 posts
CVE-2025-65877 - Lvzhou CMS SQL Injection Vulnerability https://cvefeed.io/vuln/detail/CVE-2025-65877
##updated 2025-12-04T17:15:08.283000
1 posts
Two new advisories from Nvidia, both high severity:
- CVE-2025-33211 and CVE-2025-33201: NVIDIA Triton Inference Server https://nvidia.custhelp.com/app/answers/detail/a_id/5734
- CVE-2025-33208: NVIDIA TAO https://nvidia.custhelp.com/app/answers/detail/a_id/5730 #Nvidia #infosec #vulnerability
##updated 2025-12-04T00:32:03
1 posts
updated 2025-12-03T21:32:01
8 posts
3 repos
https://github.com/hev0x/CVE-2021-26828_ScadaBR_RCE
US CISA Flags Critical OpenPLC ScadaBR Vulnerabilities Impacting Industrial Systems
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added two significant vulnerabilities in OpenPLC ScadaBR to its Known Exploited Vulnerabilities (KEV) catalog, signaling a heightened risk for industrial control systems across both public and private sectors. These flaws, identified as CVE-2021-26828 and CVE-2021-26829, expose critical weaknesses that could allow…
##🚨CVE-2021-26828: OpenPLC ScadaBR Unrestricted Upload of File with Dangerous Type Vulnerability has been added to the CISA KEV Catalog
Vendor: OpenPLC
Product: ScadaBR
CVSS: 8.8
🚨 [CISA-2025:1203] CISA Adds One Known Exploited Vulnerability to Catalog (https://secdb.nttzen.cloud/security-advisory/detail/CISA-2025:1203)
CISA has added one new vulnerability to its Known Exploited Vulnerabilities Catalog, based on evidence of active exploitation. These types of vulnerabilities are a frequent attack vector for malicious cyber actors and pose significant risk to the federal enterprise.
⚠️ CVE-2021-26828 (https://secdb.nttzen.cloud/cve/detail/CVE-2021-26828)
- Name: OpenPLC ScadaBR Unrestricted Upload of File with Dangerous Type Vulnerability
- Action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- Known To Be Used in Ransomware Campaigns? Unknown
- Vendor: OpenPLC
- Product: ScadaBR
- Notes: This vulnerability could affect an open-source component, third-party library, protocol, or proprietary implementation that could be used by different products. For more information, please see: https://github.com/SCADA-LTS/Scada-LTS/pull/2174 ; https://nvd.nist.gov/vuln/detail/CVE-2021-26828
#SecDB #InfoSec #CVE #CISA_KEV #cisa_20251203 #cisa20251203 #cve_2021_26828 #cve202126828
##Sure CISA says (today) CVE-2021-26828 OpenPLC ScadaBR Unrestricted Upload of File with Dangerous Type Vulnerability is rly bad and being actively exploited by real attackers, but WILL MY TEAM DO THAT?! Nope. They're part of the celebrity vuln. cult.
##CVE ID: CVE-2021-26828
Vendor: OpenPLC
Product: ScadaBR
Date Added: 2025-12-03
Notes: This vulnerability could affect an open-source component, third-party library, protocol, or proprietary implementation that could be used by different products. For more information, please see: https://github.com/SCADA-LTS/Scada-LTS/pull/2174 ; https://nvd.nist.gov/vuln/detail/CVE-2021-26828
CVE URL: https://nvd.nist.gov/vuln/detail/CVE-2021-26828
🚨CVE-2021-26828: OpenPLC ScadaBR Unrestricted Upload of File with Dangerous Type Vulnerability has been added to the CISA KEV Catalog
Vendor: OpenPLC
Product: ScadaBR
CVSS: 8.8
Sure CISA says (today) CVE-2021-26828 OpenPLC ScadaBR Unrestricted Upload of File with Dangerous Type Vulnerability is rly bad and being actively exploited by real attackers, but WILL MY TEAM DO THAT?! Nope. They're part of the celebrity vuln. cult.
##CVE ID: CVE-2021-26828
Vendor: OpenPLC
Product: ScadaBR
Date Added: 2025-12-03
Notes: This vulnerability could affect an open-source component, third-party library, protocol, or proprietary implementation that could be used by different products. For more information, please see: https://github.com/SCADA-LTS/Scada-LTS/pull/2174 ; https://nvd.nist.gov/vuln/detail/CVE-2021-26828
CVE URL: https://nvd.nist.gov/vuln/detail/CVE-2021-26828
updated 2025-12-03T21:31:11
2 posts
1 repos
BoF in SmallBASIC.
##BoF in SmallBASIC.
##updated 2025-12-03T21:31:11
4 posts
Hold up.
Wait a minute.
Something ain't right.
https://community.openvpn.net/Security%20Announcements/CVE-2025-13086
##Improper validation of source IP addresses in OpenVPN version 2.6.0 through 2.7_rc1 allows an attacker to open a session from a different IP address which did not initiate the connection resulting in a denial of service for the originating client.
Hold up.
Wait a minute.
Something ain't right.
https://community.openvpn.net/Security%20Announcements/CVE-2025-13086
##Improper validation of source IP addresses in OpenVPN version 2.6.0 through 2.7_rc1 allows an attacker to open a session from a different IP address which did not initiate the connection resulting in a denial of service for the originating client.
OpenVPN releases security updates patching HMAC bypass, buffer over-read, and Windows DoS flaws
OpenVPN has patched three vulnerabilities including two critical flaws (CVE-2025-13086 and CVE-2025-12106, both CVSS 9.1): a logic error that bypasses HMAC verification allowing unauthorized TLS sessions from any IP address, and an IPv6 parsing flaw causing buffer over-reads.
**Plan a quick update of your OpenVPN to version 2.6.17 (stable) or 2.7_rc3 (development) to fix three interesting security flaws. This is not critical, but a wise choice to patch, since OpenVPN is exposed to the internet and someone will find an exploit.**
#cybersecurity #infosec #advisory #vulnerability
https://beyondmachines.net/event_details/openvpn-releases-security-updates-patching-hmac-bypass-buffer-over-read-and-windows-dos-flaws-1-o-b-m-6/gD2P6Ple2L
updated 2025-12-03T21:31:10
1 posts
Two new advisories from Nvidia, both high severity:
- CVE-2025-33211 and CVE-2025-33201: NVIDIA Triton Inference Server https://nvidia.custhelp.com/app/answers/detail/a_id/5734
- CVE-2025-33208: NVIDIA TAO https://nvidia.custhelp.com/app/answers/detail/a_id/5730 #Nvidia #infosec #vulnerability
##updated 2025-12-03T21:31:04
1 posts
CVE-2025-41012 - Unauthorized access vulnerability in TCMAN GIM https://cvefeed.io/vuln/detail/CVE-2025-41012
##updated 2025-12-03T21:31:04
1 posts
CVE-2025-11788 - Heap-based buffer overflow vulnerability in Circutor SGE-PLC1000/SGE-PLC50 https://cvefeed.io/vuln/detail/CVE-2025-11788
##updated 2025-12-03T20:22:29.533000
1 posts
CVE-2025-65358 - Edoc Doctor Appointment System SQL Injection Vulnerability https://cvefeed.io/vuln/detail/CVE-2025-65358
##updated 2025-12-03T19:54:41.300000
1 posts
CVE-2025-41013 - SQL injection vulnerability in TCMAN GIM https://cvefeed.io/vuln/detail/CVE-2025-41013
##updated 2025-12-03T19:16:37.603000
1 posts
CVE-2025-11787 - Command injection vulnerability in Circutor SGE-PLC1000/SGE-PLC50 https://cvefeed.io/vuln/detail/CVE-2025-11787
##updated 2025-12-03T18:30:37
1 posts
🔥 CVE-2025-34319: CRITICAL OS Command Injection in TOTOLINK N300RT (firmware < V3.4.0-B20250430). Unauthenticated RCE via Boa formWsc—patch ASAP or segment & restrict access. Monitor for exploit attempts! https://radar.offseq.com/threat/cve-2025-34319-cwe-78-improper-neutralization-of-s-9672dc71 #OffSeq #CVE202534319 #IoTSecurity
##updated 2025-12-03T18:30:37
2 posts
Go hack more Plesk shit.
##Go hack more Plesk shit.
##updated 2025-12-03T18:30:24
1 posts
2 repos
CVE-2025-13390 - WP Directory Kit <= 1.4.4 - Authentication Bypass to Privilege Escalation via Account Takeover https://cvefeed.io/vuln/detail/CVE-2025-13390
##updated 2025-12-03T18:15:47.200000
37 posts
23 repos
https://github.com/ZihxS/check-react-rce-cve-2025-55182
https://github.com/Malayke/Next.js-RSC-RCE-Scanner-CVE-2025-66478
https://github.com/hackersatyamrastogi/react2shell-ultimate
https://github.com/freeqaz/react2shell
https://github.com/BankkRoll/Quickcheck-CVE-2025-55182-React-and-CVE-2025-66478-Next.js
https://github.com/jctommasi/react2shellVulnApp
https://github.com/nehkark/CVE-2025-55182
https://github.com/assetnote/react2shell-scanner
https://github.com/imbas007/POC-CVE-2025-66478
https://github.com/sh1ro8/react2shell
https://github.com/pyroxenites/Nextjs_RCE_Exploit_Tool
https://github.com/mattcbarrett/check-cve-2025-66478
https://github.com/Saturate/CVE-2025-55182-Scanner
https://github.com/abtonc/next-cve-2025-66478
https://github.com/CymulateResearch/React2Shell-Scanner
https://github.com/tobiasGuta/Next.js-RSC-RCE-Scanner-Burp-Suite-Extension
https://github.com/songsanggggg/CVE-2025-55182
https://github.com/onlylovetx/CVE-2025-55182-CVE-2025-66478-Exploit-GUI
https://github.com/wangxso/CVE-2025-66478-POC
https://github.com/heiheishushu/rsc_detect_CVE-2025-55182
https://github.com/pax-k/react2shell-CVE-2025-55182-full-rce-script
RIP javascript devs
https://github.com/Malayke/Next.js-RSC-RCE-Scanner-CVE-2025-66478
##🚨 CVE-2025-66478: Next.js RSC RCE Scanner and POC/Exploit Collection
A command-line scanner for batch detection of Next.js application versions and determining if they are affected by CVE-2025-66478 vulnerability.
GitHub: https://github.com/Malayke/Next.js-RSC-RCE-Scanner-CVE-2025-66478
##Progress Sitefinity Next.js Renderer appears to be vulnerable to this React vuln. React2Shell? Is that what everyone is calling it?
##Critical RCE vulnerability (React2shell) found in React Server Components and Next.js. Affects many modern web apps. Patch immediately or deploy WAF rules. Exploitation is imminent.
##🚨 ALERT! 🚨 #NextJS finally achieved what we all thought impossible: a CVSS 10.0 vulnerability! 🎯 Bravo, they've hit the bullseye of FAIL! 🙈 It's always heartwarming when devs leave the #backdoor open for #hackers to make themselves at home. 🏠🔓
https://nextjs.org/blog/CVE-2025-66478 #Vulnerability #CVSS10 #SecurityFail #HackerNews #ngated
NextJS Security Vulnerability
https://nextjs.org/blog/CVE-2025-66478
#HackerNews #NextJS #Security #Vulnerability #NextJS #Security #Vulnerability #Cybersecurity #WebDevelopment #SoftwareSecurity #CVE2025
##NextJS Security Vulnerability
https://nextjs.org/blog/CVE-2025-66478
#ycombinator
You've probably heard about the CVE-2025-66478 vulnerability for React and that the vulnerability also affects Next.js. It's really important you make sure you are patched!
Here's the Next.js article on it: https://nextjs.org/blog/CVE-2025-66478
Here's the React article on it: https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
Get your updates done, even if you don't use React Server components!
##NextJS Security Vulnerability
##NextJS Security Vulnerability - https://nextjs.org/blog/CVE-2025-66478
##⚠️ Critical RCE Vulnerabilities Discovered in React & Next.js | Wiz Blog
「 Wiz data indicates that 39% of cloud environments contain instances of Next.js or React in versions vulnerable to CVE-2025-55182 and/or CVE-2025-66478. Regarding Next.js, the framework itself is present in 69% of environments. Notably, 61% of those environments have public applications running Next.js, meaning that 44% of all cloud environments have publicly exposed Next.js instances 」
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
##📢 Next.js RSC : détection fiable d’une RCE (CVE-2025-55182 & CVE-2025-66478)
📝 Selon Searchlight Cyber (billet de recherche, 4 décembre 2025), une vulnérabilité de type RCE affectan...
📖 cyberveille : https://cyberveille.ch/posts/2025-12-04-next-js-rsc-detection-fiable-dune-rce-cve-2025-55182-cve-2025-66478/
🌐 source : https://slcyber.io/research-center/high-fidelity-detection-mechanism-for-rsc-next-js-rce-cve-2025-55182-cve-2025-66478/
#CVE_2025_55182_66478 #IOC #Cyberveille
Critical remote code execution vulnerabilities reported in React and Next.js
React and Next.js have patched two critical remote code execution vulnerabilities (CVE-2025-55182 and CVE-2025-66478) in React Server Components that allow unauthenticated attackers to execute arbitrary code through specially crafted HTTP requests exploiting insecure deserialization. Default configurations are vulnerable with near 100% exploitation reliability.
**If you're running React 19.x or Next.js 15.x/16.x (or frameworks using React Server Components like Waku or Redwood), attackers can take complete control of your servers with no authentication needed. Plan a VERY QUICK upgrade to the latest patched versions - this is the only fix available, so prioritize this update now.**
#cybersecurity #infosec #advisory #vulnerability
https://beyondmachines.net/event_details/critical-remote-code-execution-vulnerabilities-reported-in-react-and-next-js-j-3-6-0-d/gD2P6Ple2L
High Fidelity Detection Mechanism for RSC/Next.js RCE (CVE-2025-55182 & CVE-2025-66478) https://slcyber.io/research-center/high-fidelity-detection-mechanism-for-rsc-next-js-rce-cve-2025-55182-cve-2025-66478/
##CVE-2025-66478: RCE in React Server Components
Bulletin ID: AWS-2025-030 Scope: AWS Content Type: Important (requires attention) Publication Date: 2025/12/03 20:00 PM PST
Description:
AWS is aware of the recently disclosed CVE-2025-55182 which affects the React Server Flight...
https://aws.amazon.com/security/security-bulletins/rss/aws-2025-030/
##Happy Holidays Everyone!
##A maximum-severity security flaw has been disclosed in React Server Components (RSC) that, if successfully exploited, could result in remote code execution.
The vulnerability, tracked as CVE-2025-55182, carries a CVSS score of 10.0.
The vulnerability impacts versions 19.0, 19.1.0, 19.1.1, and 19.2.0 of the following npm packages -
It's worth noting that the vulnerability also affects Next.js using App Router. The issue has been assigned the CVE identifier CVE-2025-66478 (CVSS score: 10.0). It impacts versions >=14.3.0-canary.77, >=15, and >=16. Patched versions are 16.0.7, 15.5.7, 15.4.8, 15.3.6, 15.2.6, 15.1.9, and 15.0.5.
https://thehackernews.com/2025/12/critical-rsc-bugs-in-react-and-nextjs.html
#REACTjs #NEXTjs #infosec #cybersecurity #CVE202566478 #CVE202555182 #ShitIsOnFireYo
##@hrbrmstr Can we kill Next.js while we're at it? https://trends.builtwith.com/websitelist/Next.js
https://nextjs.org/blog/CVE-2025-66478
@GossiTheDog Worth mentioning that Next.js appears affected 15.x and 16.x.
##New.
This relates to CVE-2025-55182 and CVE-2025-66478. Wiz: Critical Vulnerabilities in React and Next.js: everything you need to know https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182 @wiz #infosec #vulnerabilities #threatresearch
##RCE in React Server Components, impacting React and Next.js. I usually don't say this, but patch right freakin' now. The React CVE listing (CVE-2025-55182) is a perfect 10.
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
https://nextjs.org/blog/CVE-2025-66478
RIP javascript devs
https://github.com/Malayke/Next.js-RSC-RCE-Scanner-CVE-2025-66478
##🚨 CVE-2025-66478: Next.js RSC RCE Scanner and POC/Exploit Collection
A command-line scanner for batch detection of Next.js application versions and determining if they are affected by CVE-2025-66478 vulnerability.
GitHub: https://github.com/Malayke/Next.js-RSC-RCE-Scanner-CVE-2025-66478
##Progress Sitefinity Next.js Renderer appears to be vulnerable to this React vuln. React2Shell? Is that what everyone is calling it?
##NextJS Security Vulnerability
https://nextjs.org/blog/CVE-2025-66478
#HackerNews #NextJS #Security #Vulnerability #NextJS #Security #Vulnerability #Cybersecurity #WebDevelopment #SoftwareSecurity #CVE2025
##NextJS Security Vulnerability
https://nextjs.org/blog/CVE-2025-66478
#ycombinator
NextJS Security Vulnerability
##⚠️ Critical RCE Vulnerabilities Discovered in React & Next.js | Wiz Blog
「 Wiz data indicates that 39% of cloud environments contain instances of Next.js or React in versions vulnerable to CVE-2025-55182 and/or CVE-2025-66478. Regarding Next.js, the framework itself is present in 69% of environments. Notably, 61% of those environments have public applications running Next.js, meaning that 44% of all cloud environments have publicly exposed Next.js instances 」
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
##📢 Next.js RSC : détection fiable d’une RCE (CVE-2025-55182 & CVE-2025-66478)
📝 Selon Searchlight Cyber (billet de recherche, 4 décembre 2025), une vulnérabilité de type RCE affectan...
📖 cyberveille : https://cyberveille.ch/posts/2025-12-04-next-js-rsc-detection-fiable-dune-rce-cve-2025-55182-cve-2025-66478/
🌐 source : https://slcyber.io/research-center/high-fidelity-detection-mechanism-for-rsc-next-js-rce-cve-2025-55182-cve-2025-66478/
#CVE_2025_55182_66478 #IOC #Cyberveille
Critical remote code execution vulnerabilities reported in React and Next.js
React and Next.js have patched two critical remote code execution vulnerabilities (CVE-2025-55182 and CVE-2025-66478) in React Server Components that allow unauthenticated attackers to execute arbitrary code through specially crafted HTTP requests exploiting insecure deserialization. Default configurations are vulnerable with near 100% exploitation reliability.
**If you're running React 19.x or Next.js 15.x/16.x (or frameworks using React Server Components like Waku or Redwood), attackers can take complete control of your servers with no authentication needed. Plan a VERY QUICK upgrade to the latest patched versions - this is the only fix available, so prioritize this update now.**
#cybersecurity #infosec #advisory #vulnerability
https://beyondmachines.net/event_details/critical-remote-code-execution-vulnerabilities-reported-in-react-and-next-js-j-3-6-0-d/gD2P6Ple2L
High Fidelity Detection Mechanism for RSC/Next.js RCE (CVE-2025-55182 & CVE-2025-66478) https://slcyber.io/research-center/high-fidelity-detection-mechanism-for-rsc-next-js-rce-cve-2025-55182-cve-2025-66478/
##CVE-2025-66478: RCE in React Server Components
Bulletin ID: AWS-2025-030 Scope: AWS Content Type: Important (requires attention) Publication Date: 2025/12/03 20:00 PM PST
Description:
AWS is aware of the recently disclosed CVE-2025-55182 which affects the React Server Flight...
https://aws.amazon.com/security/security-bulletins/rss/aws-2025-030/
##A maximum-severity security flaw has been disclosed in React Server Components (RSC) that, if successfully exploited, could result in remote code execution.
The vulnerability, tracked as CVE-2025-55182, carries a CVSS score of 10.0.
The vulnerability impacts versions 19.0, 19.1.0, 19.1.1, and 19.2.0 of the following npm packages -
It's worth noting that the vulnerability also affects Next.js using App Router. The issue has been assigned the CVE identifier CVE-2025-66478 (CVSS score: 10.0). It impacts versions >=14.3.0-canary.77, >=15, and >=16. Patched versions are 16.0.7, 15.5.7, 15.4.8, 15.3.6, 15.2.6, 15.1.9, and 15.0.5.
https://thehackernews.com/2025/12/critical-rsc-bugs-in-react-and-nextjs.html
#REACTjs #NEXTjs #infosec #cybersecurity #CVE202566478 #CVE202555182 #ShitIsOnFireYo
##@hrbrmstr Can we kill Next.js while we're at it? https://trends.builtwith.com/websitelist/Next.js
https://nextjs.org/blog/CVE-2025-66478
@GossiTheDog Worth mentioning that Next.js appears affected 15.x and 16.x.
##New.
This relates to CVE-2025-55182 and CVE-2025-66478. Wiz: Critical Vulnerabilities in React and Next.js: everything you need to know https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182 @wiz #infosec #vulnerabilities #threatresearch
##RCE in React Server Components, impacting React and Next.js. I usually don't say this, but patch right freakin' now. The React CVE listing (CVE-2025-55182) is a perfect 10.
https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
https://nextjs.org/blog/CVE-2025-66478
updated 2025-12-03T16:59:22
1 posts
CVE-2025-65657 - FeehiCMS Remote Code Execution via Unrestricted File Upload https://cvefeed.io/vuln/detail/CVE-2025-65657
##updated 2025-12-03T15:31:32
1 posts
CVE-2025-65656 - Apache Dcat-Admin File Inclusion Vulnerability https://cvefeed.io/vuln/detail/CVE-2025-65656
##updated 2025-12-03T15:31:32
1 posts
updated 2025-12-03T15:30:36
1 posts
CVE-2025-13949 - ProudMuBai GoFilm FileController.go SingleUpload unrestricted upload https://cvefeed.io/vuln/detail/CVE-2025-13949
##updated 2025-12-03T15:30:36
1 posts
CVE-2025-13948 - opsre go-ldap-admin JWT docker-compose.yaml hard-coded key https://cvefeed.io/vuln/detail/CVE-2025-13948
##updated 2025-12-03T15:30:36
1 posts
CVE-2025-13401 - Autoptimize <= 3.1.13 - Authenticated (Contributor+) Stored Cross-Site Scripting https://cvefeed.io/vuln/detail/CVE-2025-13401
##updated 2025-12-03T15:30:36
1 posts
CVE-2025-13109 - HUSKY – Products Filter Professional for WooCommerce <= 1.3.7.2 - Authenticated (Subscriber+) Insecure Direct Object Reference via 'woof_add_query/woof_remove_query' https://cvefeed.io/vuln/detail/CVE-2025-13109
##updated 2025-12-03T15:30:36
1 posts
CVE-2025-12887 - Post SMTP – Complete SMTP Solution with Logs, Alerts, Backup SMTP & Mobile App <= 3.6.1 - Missing Authorization to Authenticated (Subscriber+) OAuth Token Update https://cvefeed.io/vuln/detail/CVE-2025-12887
##updated 2025-12-03T14:18:29
1 posts
CVE-2025-65186 - Grav CMS Stored XSS Vulnerability https://cvefeed.io/vuln/detail/CVE-2025-65186
##updated 2025-12-03T12:30:20
1 posts
CVE-2025-39665 - Livestatus Injection in dynmaps https://cvefeed.io/vuln/detail/CVE-2025-39665
##updated 2025-12-03T09:31:18
1 posts
CVE-2025-13945 - Improperly Controlled Sequential Memory Allocation in Wireshark https://cvefeed.io/vuln/detail/CVE-2025-13945
##updated 2025-12-03T09:31:13
2 posts
1 repos
CVE-2025-12744 - Abrt: command-injection in abrt leading to local privilege escalation https://cvefeed.io/vuln/detail/CVE-2025-12744
##CVE-2025-12744 - Abrt: command-injection in abrt leading to local privilege escalation https://cvefeed.io/vuln/detail/CVE-2025-12744
##updated 2025-12-03T06:31:20
1 posts
CVE-2025-13495 - FluentCart A New Era of eCommerce <= 1.3.1 - Authenticated (Administrator+) SQL Injection via 'groupKey' Parameter https://cvefeed.io/vuln/detail/CVE-2025-13495
##updated 2025-12-03T06:31:16
1 posts
CVE-2025-10304 - Everest Backup – WordPress Cloud Backup, Migration, Restore & Cloning Plugin <= 2.3.8 - Missing Authorization to Unauthenticated Backup Failure https://cvefeed.io/vuln/detail/CVE-2025-10304
##updated 2025-12-03T03:31:21
1 posts
CVE-2025-13645 - Modula 2.13.1 - 2.13.2 - Authenticated (Author+) Arbitrary File Deletion https://cvefeed.io/vuln/detail/CVE-2025-13645
##updated 2025-12-03T03:31:21
1 posts
CVE-2025-55181 - Apache Quic HTTP Denial of Service (DoS) https://cvefeed.io/vuln/detail/CVE-2025-55181
##updated 2025-12-03T00:31:35
1 posts
CVE-2025-65380 - PHPGurukul Billing System SQL Injection Vulnerability https://cvefeed.io/vuln/detail/CVE-2025-65380
##updated 2025-12-03T00:31:35
1 posts
CVE-2025-65379 - PHPGurukul Billing System SQL Injection Vulnerability https://cvefeed.io/vuln/detail/CVE-2025-65379
##updated 2025-12-02T22:16:08.850000
1 posts
CVE-2025-64460 - Potential denial-of-service vulnerability in XML serializer text extraction https://cvefeed.io/vuln/detail/CVE-2025-64460
##updated 2025-12-02T21:32:34
1 posts
CVE-2025-64070 - Sourcecodester Student Grades Management System Cross Site Scripting (XSS) https://cvefeed.io/vuln/detail/CVE-2025-64070
##updated 2025-12-02T21:32:33
2 posts
Microsoft has updated its security guide:
New: CVE-2023-53292: blk-mq: fix NULL dereference on q->elevator in blk_mq_elv_switch_none https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-53292
New: CVE-2023-53261: coresight: Fix memory leak in acpi_buffer->pointer https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-53261
New: CVE-2022-50266: kprobes: Fix check for probe enabled in kill_kprobe() https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-50266 #Microsoft #infosec #Linux #vulnerability
##Microsoft has updated its security guide:
New: CVE-2023-53292: blk-mq: fix NULL dereference on q->elevator in blk_mq_elv_switch_none https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-53292
New: CVE-2023-53261: coresight: Fix memory leak in acpi_buffer->pointer https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-53261
New: CVE-2022-50266: kprobes: Fix check for probe enabled in kill_kprobe() https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-50266 #Microsoft #infosec #Linux #vulnerability
##updated 2025-12-02T21:31:42
4 posts
Critical remote code execution flaw reported in Industrial Video & Control Longwatch surveillance system
CISA is reporting a critical vulnerability (CVE-2025-13658) in Industrial Video & Control's Longwatch video surveillance platform that allows unauthenticated attackers to execute arbitrary code and gain full system control through an exposed HTTP endpoint. The flaw affects versions 6.309-6.334.
**This one is very important! If you have Industrial Video & Control Longwatch surveillance systems, ensure these devices are isolated from the internet and only accessible from trusted networks. Then plan a very quick upgrade to version 6.335 or later. Your Longwatch is vulnerable and very easy to hack, so don't delay.**
#cybersecurity #infosec #advisory #vulnerability
https://beyondmachines.net/event_details/critical-remote-code-execution-flaw-reported-in-industrial-video-control-longwatch-surveillance-system-2-a-w-v-p/gD2P6Ple2L
Always look at the credits in CVE records, they’re full of insightful details.
I particularly enjoyed this one. By the way, in Vulnerability Lookup we also have a nice display of the actual credits: finder, coordinator, and so on.
🔗 https://vulnerability.circl.lu/vuln/cve-2025-13658
"A vulnerability in Longwatch devices allows unauthenticated HTTP GET requests to execute arbitrary code via an exposed endpoint, due to the absence of code signing and execution controls. Exploitation results in SYSTEM-level privileges.
"
CVE-2025-13658 - Industrial Video & Control Longwatch has a Code Injection vulnerability https://cvefeed.io/vuln/detail/CVE-2025-13658
##CVE-2025-13658 - Industrial Video & Control Longwatch has a Code Injection vulnerability https://cvefeed.io/vuln/detail/CVE-2025-13658
##updated 2025-12-02T21:31:42
2 posts
CVE-2025-64778 - Mirion Medical EC2 Software NMIS BioDose Use of Hard-coded Credentials https://cvefeed.io/vuln/detail/CVE-2025-64778
##CVE-2025-64778 - Mirion Medical EC2 Software NMIS BioDose Use of Hard-coded Credentials https://cvefeed.io/vuln/detail/CVE-2025-64778
##updated 2025-12-02T21:31:42
2 posts
CVE-2025-64642 - Mirion Medical EC2 Software NMIS BioDose Incorrect Permission Assignment for Critical Resource https://cvefeed.io/vuln/detail/CVE-2025-64642
##CVE-2025-64642 - Mirion Medical EC2 Software NMIS BioDose Incorrect Permission Assignment for Critical Resource https://cvefeed.io/vuln/detail/CVE-2025-64642
##updated 2025-12-02T21:31:42
2 posts
CVE-2025-61940 - Mirion Medical EC2 Software NMIS BioDose Use of Client-Side Authentication https://cvefeed.io/vuln/detail/CVE-2025-61940
##CVE-2025-61940 - Mirion Medical EC2 Software NMIS BioDose Use of Client-Side Authentication https://cvefeed.io/vuln/detail/CVE-2025-61940
##updated 2025-12-02T21:31:37
2 posts
Critical authentication bypass flaw reported in Iskra Smart Metering gateways
CISA is reporting a critical missing authentication vulnerability (CVE-2025-13510) in all versions of Iskra iHUB and iHUB Lite smart metering gateways that allows unauthenticated remote attackers to perform privileged operations via an exposed web management interface. No patch is currently available. The vendor has not responded to CISA.
**If you are using Iskra iHUB and iHUB Lite smart metering gateways, make sure that they are isolated from the internet and placed behind firewalls on trusted networks only. Since no patch is available, require VPN access for any remote management and closely monitor these devices for unauthorized access attempts.**
#cybersecurity #infosec #advisory #vulnerability
https://beyondmachines.net/event_details/critical-authentication-bypass-flaw-reported-in-iskra-smart-metering-gateways-a-4-y-a-9/gD2P6Ple2L
CVE-2025-13510 - Iskra iHUB and iHUB Lite has a Missing Authentication for Critical Function vulnerabilitiy https://cvefeed.io/vuln/detail/CVE-2025-13510
##updated 2025-12-02T21:31:37
1 posts
CVE-2025-13542 - DesignThemes LMS <= 1.0.4 - Unauthenticated Privilege Escalation https://cvefeed.io/vuln/detail/CVE-2025-13542
##updated 2025-12-02T21:31:37
1 posts
lolwut
https://access.redhat.com/security/cve/CVE-2025-57850
##This issue stems from the
/etc/passwdfile being created with group-writable permissions during build time.
updated 2025-12-02T21:31:37
1 posts
CVE-2025-34352 - JumpCloud Remote Assist < 0.317.0 Arbitrary File Write/Delete via Insecure Temp Directory https://cvefeed.io/vuln/detail/CVE-2025-34352
##updated 2025-12-02T21:11:36
2 posts
CVE-2025-13827 - GrapesJsBuilder File Upload allows all file uploads https://cvefeed.io/vuln/detail/CVE-2025-13827
##CVE-2025-13827 - GrapesJsBuilder File Upload allows all file uploads https://cvefeed.io/vuln/detail/CVE-2025-13827
##updated 2025-12-02T21:07:03
1 posts
CVE-2025-64750 - Singluarity ineffectively applies of selinux / apparmor LSM process labels https://cvefeed.io/vuln/detail/CVE-2025-64750
##updated 2025-12-02T20:45:00.577000
2 posts
Microsoft has updated its security guide:
New: CVE-2023-53292: blk-mq: fix NULL dereference on q->elevator in blk_mq_elv_switch_none https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-53292
New: CVE-2023-53261: coresight: Fix memory leak in acpi_buffer->pointer https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-53261
New: CVE-2022-50266: kprobes: Fix check for probe enabled in kill_kprobe() https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-50266 #Microsoft #infosec #Linux #vulnerability
##Microsoft has updated its security guide:
New: CVE-2023-53292: blk-mq: fix NULL dereference on q->elevator in blk_mq_elv_switch_none https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-53292
New: CVE-2023-53261: coresight: Fix memory leak in acpi_buffer->pointer https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-53261
New: CVE-2022-50266: kprobes: Fix check for probe enabled in kill_kprobe() https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-50266 #Microsoft #infosec #Linux #vulnerability
##updated 2025-12-02T20:15:52.670000
1 posts
CVE-2025-65187 - CiviCRM Stored XSS https://cvefeed.io/vuln/detail/CVE-2025-65187
##updated 2025-12-02T20:15:51.837000
1 posts
CVE-2025-63872 - DeepSeek XSS Vector Injection https://cvefeed.io/vuln/detail/CVE-2025-63872
##updated 2025-12-02T19:07:08.450000
2 posts
Microsoft has updated its security guide:
New: CVE-2023-53292: blk-mq: fix NULL dereference on q->elevator in blk_mq_elv_switch_none https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-53292
New: CVE-2023-53261: coresight: Fix memory leak in acpi_buffer->pointer https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-53261
New: CVE-2022-50266: kprobes: Fix check for probe enabled in kill_kprobe() https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-50266 #Microsoft #infosec #Linux #vulnerability
##Microsoft has updated its security guide:
New: CVE-2023-53292: blk-mq: fix NULL dereference on q->elevator in blk_mq_elv_switch_none https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-53292
New: CVE-2023-53261: coresight: Fix memory leak in acpi_buffer->pointer https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-53261
New: CVE-2022-50266: kprobes: Fix check for probe enabled in kill_kprobe() https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-50266 #Microsoft #infosec #Linux #vulnerability
##updated 2025-12-02T17:16:29.163000
2 posts
CVE-2025-13828 - Mautic user without privileged access to the Marketplace can install and uninstall composer packages https://cvefeed.io/vuln/detail/CVE-2025-13828
##CVE-2025-13828 - Mautic user without privileged access to the Marketplace can install and uninstall composer packages https://cvefeed.io/vuln/detail/CVE-2025-13828
##updated 2025-12-01T21:31:27
1 posts
OpenVPN releases security updates patching HMAC bypass, buffer over-read, and Windows DoS flaws
OpenVPN has patched three vulnerabilities including two critical flaws (CVE-2025-13086 and CVE-2025-12106, both CVSS 9.1): a logic error that bypasses HMAC verification allowing unauthorized TLS sessions from any IP address, and an IPv6 parsing flaw causing buffer over-reads.
**Plan a quick update of your OpenVPN to version 2.6.17 (stable) or 2.7_rc3 (development) to fix three interesting security flaws. This is not critical, but a wise choice to patch, since OpenVPN is exposed to the internet and someone will find an exploit.**
#cybersecurity #infosec #advisory #vulnerability
https://beyondmachines.net/event_details/openvpn-releases-security-updates-patching-hmac-bypass-buffer-over-read-and-windows-dos-flaws-1-o-b-m-6/gD2P6Ple2L
updated 2025-12-01T15:23:18.697000
1 posts
US CISA Flags Critical OpenPLC ScadaBR Vulnerabilities Impacting Industrial Systems
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added two significant vulnerabilities in OpenPLC ScadaBR to its Known Exploited Vulnerabilities (KEV) catalog, signaling a heightened risk for industrial control systems across both public and private sectors. These flaws, identified as CVE-2021-26828 and CVE-2021-26829, expose critical weaknesses that could allow…
##updated 2025-11-25T03:30:26
2 posts
1 repos
Critical remote code execution flaw in Sneeit Framework WordPress Plugin actively exploited
A critical remote code execution vulnerability (CVE-2025-6389) in the Sneeit Framework WordPress plugin is under active exploitation. The flaw allows unauthenticated attackers to create admin accounts, upload backdoors, and fully compromise servers.
**If you're using the Sneeit Framework WordPress plugin, immediately update to version 8.4 or later. Your site is vulnerable and is actively attacked. Check your WordPress site for unauthorized administrator accounts (especially username "arudikadis") and suspicious PHP files in your uploads directory to ensure you haven't been compromised.**
#cybersecurity #infosec #attack #activeexploit
https://beyondmachines.net/event_details/critical-remote-code-execution-flaw-in-sneeit-framework-wordpress-plugin-actively-exploited-i-m-n-t-2/gD2P6Ple2L
Critical remote code execution flaw in Sneeit Framework WordPress Plugin actively exploited
A critical remote code execution vulnerability (CVE-2025-6389) in the Sneeit Framework WordPress plugin is under active exploitation. The flaw allows unauthenticated attackers to create admin accounts, upload backdoors, and fully compromise servers.
**If you're using the Sneeit Framework WordPress plugin, immediately update to version 8.4 or later. Your site is vulnerable and is actively attacked. Check your WordPress site for unauthorized administrator accounts (especially username "arudikadis") and suspicious PHP files in your uploads directory to ensure you haven't been compromised.**
#cybersecurity #infosec #attack #activeexploit
https://beyondmachines.net/event_details/critical-remote-code-execution-flaw-in-sneeit-framework-wordpress-plugin-actively-exploited-i-m-n-t-2/gD2P6Ple2L
updated 2025-11-24T21:31:06
1 posts
NVD - CVE-2018-25126 - Shenzhen NVMS-9000 firmware contains hardcoded API credentials and an OS command injection flaw https://nvd.nist.gov/vuln/detail/CVE-2018-25126
##updated 2025-11-24T15:07:32.807000
2 posts
6 repos
https://github.com/lastvocher/7zip-CVE-2025-11001
https://github.com/shalevo13/Se7enSlip
https://github.com/mbanyamer/CVE-2025-11001---7-Zip
https://github.com/pacbypass/CVE-2025-11001
7-Zip vulnerability that enables remote code execution actively exploited
A critical vulnerability in 7-Zip (CVE-2025-11001) that allows remote code execution through malicious ZIP archives is being actively exploited in the wild, targeting healthcare and financial services organizations.
**If you are using 7-Zip, this is urgent. Hackers are exploiting the 7-Zip flaw exploitable just by opening a malicious ZIP file. Update your 7-Zip software to version 25.01 or later ASAP.**
#cybersecurity #infosec #attack #activeexploit
https://beyondmachines.net/event_details/7-zip-vulnerability-that-enables-remote-code-execution-actively-exploited-f-d-5-g-j/gD2P6Ple2L
7-Zip vulnerability that enables remote code execution actively exploited
A critical vulnerability in 7-Zip (CVE-2025-11001) that allows remote code execution through malicious ZIP archives is being actively exploited in the wild, targeting healthcare and financial services organizations.
**If you are using 7-Zip, this is urgent. Hackers are exploiting the 7-Zip flaw exploitable just by opening a malicious ZIP file. Update your 7-Zip software to version 25.01 or later ASAP.**
#cybersecurity #infosec #attack #activeexploit
https://beyondmachines.net/event_details/7-zip-vulnerability-that-enables-remote-code-execution-actively-exploited-f-d-5-g-j/gD2P6Ple2L
updated 2025-11-19T21:56:39.907000
2 posts
Cisco has an updated advisory relating to CVE-2025-20289, CVE-2025-20303, CVE-2025-20304.
Medium severity, no workarounds: Cisco Identity Services Engine Reflected Cross-Site Scripting and Information Disclosure Vulnerabilities https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ise-multiple-vulns-O9BESWJH @TalosSecurity #Cisco #infosec #vulnerability
##Cisco has an updated advisory relating to CVE-2025-20289, CVE-2025-20303, CVE-2025-20304.
Medium severity, no workarounds: Cisco Identity Services Engine Reflected Cross-Site Scripting and Information Disclosure Vulnerabilities https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ise-multiple-vulns-O9BESWJH @TalosSecurity #Cisco #infosec #vulnerability
##updated 2025-11-19T15:13:13.230000
2 posts
Cisco has an updated advisory relating to CVE-2025-20289, CVE-2025-20303, CVE-2025-20304.
Medium severity, no workarounds: Cisco Identity Services Engine Reflected Cross-Site Scripting and Information Disclosure Vulnerabilities https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ise-multiple-vulns-O9BESWJH @TalosSecurity #Cisco #infosec #vulnerability
##Cisco has an updated advisory relating to CVE-2025-20289, CVE-2025-20303, CVE-2025-20304.
Medium severity, no workarounds: Cisco Identity Services Engine Reflected Cross-Site Scripting and Information Disclosure Vulnerabilities https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ise-multiple-vulns-O9BESWJH @TalosSecurity #Cisco #infosec #vulnerability
##updated 2025-11-17T21:32:22
1 posts
4 repos
https://github.com/dangokyo/CVE-2015-5119
https://github.com/jvazquez-r7/CVE-2015-5119
https://github.com/Xattam1/Adobe-Flash-Exploits_17-18
https://github.com/CiscoCXSecurity/CVE-2015-5119_walkthrough
if page is visited on old browser with Adobe Flash versions 10 through 18 (roughly) you could even use CVE-2015-5119. it's my favourite vulnerability. the exploit is so clean. Straight memory peeks and pokes from actionscript. Best. UaF. Ever.
##updated 2025-11-13T17:02:36.447000
3 posts
This affects CVE-2025-10155, CVE-2025-10156, and CVE-2025-10157.
JFrog, from yesterday: PyTorch Users at Risk: Unveiling 3 Zero-Day PickleScan Vulnerabilities https://jfrog.com/blog/unveiling-3-zero-day-vulnerabilities-in-picklescan/
More:
Infosecurity-Magazine: Critical PickleScan Vulnerabilities Expose AI Model Supply Chains https://www.infosecurity-magazine.com/news/picklescan-flaws-expose-ai-supply/ #infosec #opensource #Python #zeroday
##This affects CVE-2025-10155, CVE-2025-10156, and CVE-2025-10157.
JFrog, from yesterday: PyTorch Users at Risk: Unveiling 3 Zero-Day PickleScan Vulnerabilities https://jfrog.com/blog/unveiling-3-zero-day-vulnerabilities-in-picklescan/
More:
Infosecurity-Magazine: Critical PickleScan Vulnerabilities Expose AI Model Supply Chains https://www.infosecurity-magazine.com/news/picklescan-flaws-expose-ai-supply/ #infosec #opensource #Python #zeroday
##Critical vulnerabilities reported in PickleScan
The JFrog Security Research Team discovered three critical zero-day vulnerabilities (CVE-2025-10155, CVE-2025-10156, CVE-2025-10157) in PickleScan, a widely used ML model security scanning tool, that allow attackers to completely bypass malware detection through file extension manipulation, corrupted ZIP archives, and blacklist evasion techniques. These vulnerabilities could enable large-scale supply chain attacks by distributing malicious ML models through platforms like Hugging Face.
**If you use PickleScan to scan machine learning models, update ASAP to version 0.0.31 or later. There are three critical vulnerabilities with PoC exploits, so attackers will start pushing out malicious payloads. Also, consider using safer serialization formats like Safetensors instead of Pickle for your ML models.**
#cybersecurity #infosec #advisory #vulnerability
https://beyondmachines.net/event_details/critical-vulnerabilities-reported-in-picklescan-z-j-b-t-s/gD2P6Ple2L
updated 2025-11-11T00:30:20
2 posts
⚠️ Alert: A #WebXR flaw (CVE-2025-12443) affected Chrome, Edge, Brave, Opera and other Chromium browsers - over 4 billion devices at risk. Patch pushed - update your browser now! 🔐
Read: https://hackread.com/webxr-flaw-chromium-users-browser-update/
##⚠️ Alert: A #WebXR flaw (CVE-2025-12443) affected Chrome, Edge, Brave, Opera and other Chromium browsers - over 4 billion devices at risk. Patch pushed - update your browser now! 🔐
Read: https://hackread.com/webxr-flaw-chromium-users-browser-update/
##updated 2025-11-07T15:31:36
2 posts
3 repos
https://github.com/Chocapikk/CVE-2025-34299
🚨 Alleged Leak of Unauthorized Monsta FTP Access; CVE-2025-34299
https://darkwebinformer.com/alleged-leak-of-unauthorized-monsta-ftp-access-cve-2025-34299/
##🚨 Alleged Leak of Unauthorized Monsta FTP Access; CVE-2025-34299
https://darkwebinformer.com/alleged-leak-of-unauthorized-monsta-ftp-access-cve-2025-34299/
##updated 2025-11-05T21:15:36.513000
9 posts
1 repos
Hidden Threats in Windows Shortcuts: Microsoft Patches Nearly a Decade-Old Vulnerability
Windows users may have unknowingly been at risk for years due to a stealthy vulnerability in shortcut files. Microsoft has quietly patched a flaw that allowed attackers to conceal malicious commands in Windows shortcuts (LNK files), a weakness exploited since at least 2017. This vulnerability, now tracked as CVE-2025-9491, highlights the risks lurking in everyday system tools and…
##Une faille zero-day Windows associée aux fichiers LNK a été atténuée discrètement par Microsoft https://www.it-connect.fr/windows-zero-day-fichiers-lnk-cve-2025-9491-attenuation-microsoft/ #ActuCybersécurité #Cybersécurité #Vulnérabilité #Microsoft #Windows
##Update: Mit dem November-Update 2025 veröffentlichte Microsoft einen "Nicht-Patch-Patch". Recht lautlos wurde der Umgang von Windows mit den *lnk-Dateien geändert, wohl mit dem Ziel, die Sicherheitslücke CVE-2025-9491 zu schließen.
##Microsoft silently mitigates Windows LNK Zero-Day flaw exploited by state-backed hackers
Microsoft silently patched a high-severity Windows LNK vulnerability (CVE-2025-9491) that was actively exploited by at least 11 state-backed hacking groups and cybercrime organizations to hide malicious commands within .lNK files by padding them beyond the 260-character visibility limit. The flaw, which targeted European diplomatic entities and government departments, initially was not patched by Microsoft despite exploitation. The November 2025 fix is incomplete as it doesn't remove existing malicious code or warn users about suspicious files.
**Apply the November 2025 Windows updates immediately to partially mitigate a vulnerability, which allows hackers to hide malicious commands in .LNK shortcut files. Also, be EXTREMELY cautious opening any .LNK files from emails or downloads, especially from ZIP archives - even after updating, only open shortcuts from sources you can absolutely verify and trust.**
#cybersecurity #infosec #attack #activeexploit
https://beyondmachines.net/event_details/microsoft-silently-mitigates-windows-lnk-zero-day-flaw-exploited-by-state-backed-hackers-l-c-e-8-v/gD2P6Ple2L
Microsoft Silently Mitigates Critical Windows LNK Vulnerability Exploited in Zero-Day Attacks
A high-severity Windows vulnerability, tracked as CVE-2025-9491, has been quietly mitigated by Microsoft after being exploited in widespread zero-day attacks by both state-sponsored and cybercrime groups. This flaw allowed attackers to embed malicious commands in Windows LNK (shortcut) files, a tactic that could deliver malware and maintain persistent access to compromised…
##November 20 was the last time Microsoft's security guide was updated.
0patch blog, from yesterday: Microsoft Silently Patched CVE-2025-9491 - We Think Our Patch Provides More Security https://blog.0patch.com/2025/12/microsoft-silently-patched-cve-2025.html
More:
Security Week: Microsoft Silently Mitigated Exploited LNK Vulnerability https://www.securityweek.com/microsoft-silently-mitigated-exploited-lnk-vulnerability/ @SecurityWeek #Microsoft #vulnerability #infosec
##Une faille zero-day Windows associée aux fichiers LNK a été atténuée discrètement par Microsoft https://www.it-connect.fr/windows-zero-day-fichiers-lnk-cve-2025-9491-attenuation-microsoft/ #ActuCybersécurité #Cybersécurité #Vulnérabilité #Microsoft #Windows
##Microsoft silently mitigates Windows LNK Zero-Day flaw exploited by state-backed hackers
Microsoft silently patched a high-severity Windows LNK vulnerability (CVE-2025-9491) that was actively exploited by at least 11 state-backed hacking groups and cybercrime organizations to hide malicious commands within .lNK files by padding them beyond the 260-character visibility limit. The flaw, which targeted European diplomatic entities and government departments, initially was not patched by Microsoft despite exploitation. The November 2025 fix is incomplete as it doesn't remove existing malicious code or warn users about suspicious files.
**Apply the November 2025 Windows updates immediately to partially mitigate a vulnerability, which allows hackers to hide malicious commands in .LNK shortcut files. Also, be EXTREMELY cautious opening any .LNK files from emails or downloads, especially from ZIP archives - even after updating, only open shortcuts from sources you can absolutely verify and trust.**
#cybersecurity #infosec #attack #activeexploit
https://beyondmachines.net/event_details/microsoft-silently-mitigates-windows-lnk-zero-day-flaw-exploited-by-state-backed-hackers-l-c-e-8-v/gD2P6Ple2L
November 20 was the last time Microsoft's security guide was updated.
0patch blog, from yesterday: Microsoft Silently Patched CVE-2025-9491 - We Think Our Patch Provides More Security https://blog.0patch.com/2025/12/microsoft-silently-patched-cve-2025.html
More:
Security Week: Microsoft Silently Mitigated Exploited LNK Vulnerability https://www.securityweek.com/microsoft-silently-mitigated-exploited-lnk-vulnerability/ @SecurityWeek #Microsoft #vulnerability #infosec
##updated 2025-11-05T20:40:58
2 posts
1 repos
Perfect 10 XXE in Apache Tika tika-core. 🥳
https://lists.apache.org/thread/s5x3k93nhbkqzztp1olxotoyjpdlps9k
##Critical XXE in Apache Tika tika-core (1.13-3.2.1), tika-pdf-module (2.0.0-3.2.1) and tika-parsers (1.13-1.28.5) modules on all platforms allows an attacker to carry out XML External Entity injection via a crafted XFA file inside of a PDF. \n\nThis CVE covers the same vulnerability as in CVE-2025-54988. However, this CVE expands the scope of affected packages in two ways. \n\nFirst, while the entrypoint for the vulnerability was the tika-parser-pdf-module as reported in CVE-2025-54988, the vulnerability and its fix were in tika-core. Users who upgraded the tika-parser-pdf-module but did not upgrade tika-core to >= 3.2.2 would still be vulnerable. \n\nSecond, the original report failed to mention that in the 1.x Tika releases, the PDFParser was in the \"org.apache.tika:tika-parsers\" module.
Perfect 10 XXE in Apache Tika tika-core. 🥳
https://lists.apache.org/thread/s5x3k93nhbkqzztp1olxotoyjpdlps9k
##Critical XXE in Apache Tika tika-core (1.13-3.2.1), tika-pdf-module (2.0.0-3.2.1) and tika-parsers (1.13-1.28.5) modules on all platforms allows an attacker to carry out XML External Entity injection via a crafted XFA file inside of a PDF. \n\nThis CVE covers the same vulnerability as in CVE-2025-54988. However, this CVE expands the scope of affected packages in two ways. \n\nFirst, while the entrypoint for the vulnerability was the tika-parser-pdf-module as reported in CVE-2025-54988, the vulnerability and its fix were in tika-core. Users who upgraded the tika-parser-pdf-module but did not upgrade tika-core to >= 3.2.2 would still be vulnerable. \n\nSecond, the original report failed to mention that in the 1.x Tika releases, the PDFParser was in the \"org.apache.tika:tika-parsers\" module.
updated 2025-11-05T17:48:33
2 posts
Cisco has an updated advisory relating to CVE-2025-20289, CVE-2025-20303, CVE-2025-20304.
Medium severity, no workarounds: Cisco Identity Services Engine Reflected Cross-Site Scripting and Information Disclosure Vulnerabilities https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ise-multiple-vulns-O9BESWJH @TalosSecurity #Cisco #infosec #vulnerability
##Cisco has an updated advisory relating to CVE-2025-20289, CVE-2025-20303, CVE-2025-20304.
Medium severity, no workarounds: Cisco Identity Services Engine Reflected Cross-Site Scripting and Information Disclosure Vulnerabilities https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ise-multiple-vulns-O9BESWJH @TalosSecurity #Cisco #infosec #vulnerability
##updated 2025-11-04T15:41:31.450000
8 posts
📢 CVE-2025-8489: exploitation active d’une élévation de privilèges dans le plugin King Addons for Elementor (WordPress)
📝 S...
📖 cyberveille : https://cyberveille.ch/posts/2025-12-04-cve-2025-8489-exploitation-active-dune-elevation-de-privileges-dans-le-plugin-king-addons-for-elementor-wordpress/
🌐 source : https://www.bleepingcomputer.com/news/security/critical-flaw-in-wordpress-add-on-for-elementor-exploited-in-attacks/
#CVE_2025_8489 #King_Addons_for_Elementor #Cyberveille
⚠️ Active exploit: CRITICAL flaw in King Addons for Elementor (WordPress) lets unauth attackers register as admins (CVE-2025-8489). Patch to 51.1.35+ ASAP, audit admin accounts, monitor /wp-admin/admin-ajax.php. https://radar.offseq.com/threat/wordpress-king-addons-flaw-under-active-attack-let-7dd87bc3 #OffSeq #WordPress #infosec #vuln
##Critical flaw in WordPress add-on for Elementor exploited in attacks
Attackers are exploiting a critical-severity privilege escalation vulnerability (CVE-2025-8489) in the King Addons for Elementor plugin for...
🔗️ [Bleepingcomputer] https://link.is.it/WeissI
##Critical privilege escalation flaw in King Addons for Elementor plugin enables takeover of WordPress Sites
A critical privilege escalation vulnerability (CVE-2025-8489) in the King Addons for Elementor WordPress plugin allows unauthenticated attackers to create administrator accounts due to improper validation of user roles during registration. Over 48,000 exploitation attempts are already reported as blocked by WordFence.
**If you're using King Addons for Elementor plugin, immediately update to version 51.1.35 or later. There is an actively exploited vulnerability to create rogue administrator accounts. After updating, review all user accounts on your WordPress site and remove any suspicious or unknown administrator accounts that shouldn't be there.**
#cybersecurity #infosec #attack #activeexploit
https://beyondmachines.net/event_details/critical-privilege-escalation-flaw-in-king-addons-for-elementor-plugin-enables-takeover-of-wordpress-sites-x-e-8-d-0/gD2P6Ple2L
Critical WordPress plugin flaw alert — CVE-2025-8489 (King Addons for Elementor) is being widely exploited.
The vulnerability allowed unauthenticated attackers to assign themselves administrator roles, leading to complete site compromise.
Defiant’s telemetry shows nearly 50,000 exploitation attempts.
If you’re managing WordPress infrastructure, verifying plugin versions and reviewing registration logs is strongly recommended.
Source: https://www.securityweek.com/critical-king-addons-vulnerability-exploited-to-hack-wordpress-sites/
💬 What mitigation practices do you use to reduce plugin-related risks?
🔁 Follow for unbiased security updates.
#Infosec #WordPressSecurity #CVE20258489 #ThreatIntel #KingAddons #Elementor #WebSecurity
##Critical flaw in WordPress add-on for Elementor exploited in attacks
Attackers are exploiting a critical-severity privilege escalation vulnerability (CVE-2025-8489) in the King Addons for Elementor plugin for...
🔗️ [Bleepingcomputer] https://link.is.it/WeissI
##Critical privilege escalation flaw in King Addons for Elementor plugin enables takeover of WordPress Sites
A critical privilege escalation vulnerability (CVE-2025-8489) in the King Addons for Elementor WordPress plugin allows unauthenticated attackers to create administrator accounts due to improper validation of user roles during registration. Over 48,000 exploitation attempts are already reported as blocked by WordFence.
**If you're using King Addons for Elementor plugin, immediately update to version 51.1.35 or later. There is an actively exploited vulnerability to create rogue administrator accounts. After updating, review all user accounts on your WordPress site and remove any suspicious or unknown administrator accounts that shouldn't be there.**
#cybersecurity #infosec #attack #activeexploit
https://beyondmachines.net/event_details/critical-privilege-escalation-flaw-in-king-addons-for-elementor-plugin-enables-takeover-of-wordpress-sites-x-e-8-d-0/gD2P6Ple2L
Critical WordPress plugin flaw alert — CVE-2025-8489 (King Addons for Elementor) is being widely exploited.
The vulnerability allowed unauthenticated attackers to assign themselves administrator roles, leading to complete site compromise.
Defiant’s telemetry shows nearly 50,000 exploitation attempts.
If you’re managing WordPress infrastructure, verifying plugin versions and reviewing registration logs is strongly recommended.
Source: https://www.securityweek.com/critical-king-addons-vulnerability-exploited-to-hack-wordpress-sites/
💬 What mitigation practices do you use to reduce plugin-related risks?
🔁 Follow for unbiased security updates.
#Infosec #WordPressSecurity #CVE20258489 #ThreatIntel #KingAddons #Elementor #WebSecurity
##updated 2025-10-27T17:40:33.680000
2 posts
100 repos
https://github.com/1lann/log4shelldetect
https://github.com/alexandre-lavoie/python-log4rce
https://github.com/hackinghippo/log4shell_ioc_ips
https://github.com/redhuntlabs/Log4JHunt
https://github.com/BinaryDefense/log4j-honeypot-flask
https://github.com/korteke/log4shell-demo
https://github.com/lfama/log4j_checker
https://github.com/NCSC-NL/log4shell
https://github.com/0xDexter0us/Log4J-Scanner
https://github.com/thecyberneh/Log4j-RCE-Exploiter
https://github.com/NorthwaveSecurity/log4jcheck
https://github.com/qingtengyun/cve-2021-44228-qingteng-online-patch
https://github.com/Diverto/nse-log4shell
https://github.com/irgoncalves/f5-waf-enforce-sig-CVE-2021-44228
https://github.com/irgoncalves/f5-waf-quick-patch-cve-2021-44228
https://github.com/kozmer/log4j-shell-poc
https://github.com/infiniroot/nginx-mitigate-log4shell
https://github.com/mr-vill4in/log4j-fuzzer
https://github.com/claranet/ansible-role-log4shell
https://github.com/NS-Sp4ce/Vm4J
https://github.com/CERTCC/CVE-2021-44228_scanner
https://github.com/momos1337/Log4j-RCE
https://github.com/Jeromeyoung/log4j2burpscanner
https://github.com/boundaryx/cloudrasp-log4j2
https://github.com/sassoftware/loguccino
https://github.com/twseptian/spring-boot-log4j-cve-2021-44228-docker-lab
https://github.com/yahoo/check-log4j
https://github.com/darkarnium/Log4j-CVE-Detect
https://github.com/shamo0/CVE-2021-44228
https://github.com/leonjza/log4jpwn
https://github.com/Nanitor/log4fix
https://github.com/cisagov/log4j-scanner
https://github.com/MalwareTech/Log4jTools
https://github.com/mufeedvh/log4jail
https://github.com/nccgroup/log4j-jndi-be-gone
https://github.com/faisalfs10x/Log4j2-CVE-2021-44228-revshell
https://github.com/puzzlepeaches/Log4jHorizon
https://github.com/0xInfection/LogMePwn
https://github.com/lucab85/log4j-cve-2021-44228
https://github.com/mr-r3b00t/CVE-2021-44228
https://github.com/giterlizzi/nmap-log4shell
https://github.com/Azeemering/CVE-2021-44228-DFIR-Notes
https://github.com/CodeShield-Security/Log4JShell-Bytecode-Detector
https://github.com/thomaspatzke/Log4Pot
https://github.com/DragonSurvivalEU/RCE
https://github.com/fullhunt/log4j-scan
https://github.com/mzlogin/CVE-2021-44228-Demo
https://github.com/christophetd/log4shell-vulnerable-app
https://github.com/stripe/log4j-remediation-tools
https://github.com/LiveOverflow/log4shell
https://github.com/CrackerCat/CVE-2021-44228-Log4j-Payloads
https://github.com/mergebase/log4j-detector
https://github.com/puzzlepeaches/Log4jCenter
https://github.com/alexbakker/log4shell-tools
https://github.com/logpresso/CVE-2021-44228-Scanner
https://github.com/jas502n/Log4j2-CVE-2021-44228
https://github.com/sunnyvale-it/CVE-2021-44228-PoC
https://github.com/simonis/Log4jPatch
https://github.com/Adikso/minecraft-log4j-honeypot
https://github.com/fireeye/CVE-2021-44228
https://github.com/wortell/log4j
https://github.com/toramanemre/log4j-rce-detect-waf-bypass
https://github.com/KosmX/CVE-2021-44228-example
https://github.com/back2root/log4shell-rex
https://github.com/blake-fm/vcenter-log4j
https://github.com/Malwar3Ninja/Exploitation-of-Log4j2-CVE-2021-44228
https://github.com/ssl/scan4log4j
https://github.com/corretto/hotpatch-for-apache-log4j2
https://github.com/HyCraftHD/Log4J-RCE-Proof-Of-Concept
https://github.com/cyberxml/log4j-poc
https://github.com/Puliczek/CVE-2021-44228-PoC-log4j-bypass-words
https://github.com/puzzlepeaches/Log4jUnifi
https://github.com/tippexs/nginx-njs-waf-cve2021-44228
https://github.com/f0ng/log4j2burpscanner
https://github.com/mubix/CVE-2021-44228-Log4Shell-Hashes
https://github.com/AlexandreHeroux/Fix-CVE-2021-44228
https://github.com/dwisiswant0/look4jar
https://github.com/julian911015/Log4j-Scanner-Exploit
https://github.com/roxas-tan/CVE-2021-44228
https://github.com/rubo77/log4j_checker_beta
https://github.com/sec13b/CVE-2021-44228-POC
https://github.com/corelight/cve-2021-44228
https://github.com/tangxiaofeng7/CVE-2021-44228-Apache-Log4j-Rce
https://github.com/pedrohavay/exploit-CVE-2021-44228
https://github.com/kubearmor/log4j-CVE-2021-44228
https://github.com/Kadantte/CVE-2021-44228-poc
https://github.com/takito1812/log4j-detect
https://github.com/bigsizeme/Log4j-check
https://github.com/TaroballzChen/CVE-2021-44228-log4jVulnScanner-metasploit
https://github.com/aws-samples/kubernetes-log4j-cve-2021-44228-node-agent
https://github.com/marcourbano/CVE-2021-44228
https://github.com/toramanemre/apache-solr-log4j-CVE-2021-44228
https://github.com/greymd/CVE-2021-44228
https://github.com/justakazh/Log4j-CVE-2021-44228
https://github.com/fox-it/log4j-finder
https://github.com/HynekPetrak/log4shell-finder
https://github.com/r3kind1e/Log4Shell-obfuscated-payloads-generator
https://github.com/RedDrip7/Log4Shell_CVE-2021-44228_related_attacks_IOCs
https://github.com/qingtengyun/cve-2021-44228-qingteng-patch
Vulnerability Common Schema (replaces old CVE system)
{Product/module name or prefix}{severity number}{exploit type}
For example, CVE-2021-44228 becomes
Log4shell
CVE-2025-55182 becomes
React2shell
Simple.
##Vulnerability Common Schema (replaces old CVE system)
{Product/module name or prefix}{severity number}{exploit type}
For example, CVE-2021-44228 becomes
Log4shell
CVE-2025-55182 becomes
React2shell
Simple.
##updated 2025-10-27T17:08:52.230000
3 posts
13 repos
https://github.com/AdityaBhatt3010/CVE-2025-61882-Oracle-E-Business-Suite-Pre-Auth-RCE-Exploit
https://github.com/siddu7575/CVE-2025-61882-CVE-2025-61884
https://github.com/rxerium/CVE-2025-61882-CVE-2025-61884
https://github.com/Sachinart/CVE-2025-61882
https://github.com/GhoStZA-debug/CVE-2025-61882
https://github.com/BattalionX/http-oracle-ebs-cve-2025-61882.nse
https://github.com/AshrafZaryouh/CVE-2025-61882-Executive-Summary
https://github.com/MindflareX/CVE-2025-61882-POC
https://github.com/RootAid/CVE-2025-61882
https://github.com/watchtowrlabs/watchTowr-vs-Oracle-E-Business-Suite-CVE-2025-61882
https://github.com/Zhert-lab/CVE-2025-61882-CVE-2025-61884
University of Phoenix reports data breach caused by Oracle E-Business Suite exploit
University of Phoenix experienced a data breach after attackers exploited CVE-2025-61882, a zero-day vulnerability in Oracle E-Business Suite. The attackers maintained access from August through November 2024. The breach compromised sensitive data of students, employees, faculty, and suppliers.
****
#cybersecurity #infosec #incident #databreach
https://beyondmachines.net/event_details/university-of-phoenix-reports-data-breach-caused-by-oracle-e-business-suite-exploit-9-s-m-i-2/gD2P6Ple2L
University of Phoenix reports data breach caused by Oracle E-Business Suite exploit
University of Phoenix experienced a data breach after attackers exploited CVE-2025-61882, a zero-day vulnerability in Oracle E-Business Suite. The attackers maintained access from August through November 2024. The breach compromised sensitive data of students, employees, faculty, and suppliers.
****
#cybersecurity #infosec #incident #databreach
https://beyondmachines.net/event_details/university-of-phoenix-reports-data-breach-caused-by-oracle-e-business-suite-exploit-9-s-m-i-2/gD2P6Ple2L
University of Pennsylvania reports data breach caused by Oracle E-Business Suite exploit
The University of Pennsylvania reports a data breach in August 2025 when attackers exploited CVE-2025-61882, a critical vulnerability in Oracle E-Business Suite servers, compromising personal information of approximately 1,488 individuals. Penn was one of nearly 100 organizations affected by the Oracle EBS exploit.
****
#cybersecurity #infosec #incident #databreach
https://beyondmachines.net/event_details/university-of-pennsylvania-reports-data-breach-caused-by-oracle-e-business-suite-exploit-6-s-h-8-j/gD2P6Ple2L
updated 2025-10-27T17:06:37.437000
1 posts
9 repos
https://github.com/feely666/CVE-2024-1086
https://github.com/karim4353/CVE-2024-1086-Exploit
https://github.com/Notselwyn/CVE-2024-1086
https://github.com/xzx482/CVE-2024-1086
https://github.com/LLfam/CVE-2024-1086
https://github.com/CCIEVoice2009/CVE-2024-1086
https://github.com/kevcooper/CVE-2024-1086-checker
Detecting CVE-2024-1086: The decade-old Linux kernel vulnerability that’s being actively exploited in ransomware campaigns | Sysdig https://www.sysdig.com/blog/detecting-cve-2024-1086-the-decade-old-linux-kernel-vulnerability-thats-being-actively-exploited-in-ransomware-campaigns
##updated 2025-10-27T13:20:15.637000
1 posts
updated 2025-10-02T19:04:56
3 posts
This affects CVE-2025-10155, CVE-2025-10156, and CVE-2025-10157.
JFrog, from yesterday: PyTorch Users at Risk: Unveiling 3 Zero-Day PickleScan Vulnerabilities https://jfrog.com/blog/unveiling-3-zero-day-vulnerabilities-in-picklescan/
More:
Infosecurity-Magazine: Critical PickleScan Vulnerabilities Expose AI Model Supply Chains https://www.infosecurity-magazine.com/news/picklescan-flaws-expose-ai-supply/ #infosec #opensource #Python #zeroday
##This affects CVE-2025-10155, CVE-2025-10156, and CVE-2025-10157.
JFrog, from yesterday: PyTorch Users at Risk: Unveiling 3 Zero-Day PickleScan Vulnerabilities https://jfrog.com/blog/unveiling-3-zero-day-vulnerabilities-in-picklescan/
More:
Infosecurity-Magazine: Critical PickleScan Vulnerabilities Expose AI Model Supply Chains https://www.infosecurity-magazine.com/news/picklescan-flaws-expose-ai-supply/ #infosec #opensource #Python #zeroday
##Critical vulnerabilities reported in PickleScan
The JFrog Security Research Team discovered three critical zero-day vulnerabilities (CVE-2025-10155, CVE-2025-10156, CVE-2025-10157) in PickleScan, a widely used ML model security scanning tool, that allow attackers to completely bypass malware detection through file extension manipulation, corrupted ZIP archives, and blacklist evasion techniques. These vulnerabilities could enable large-scale supply chain attacks by distributing malicious ML models through platforms like Hugging Face.
**If you use PickleScan to scan machine learning models, update ASAP to version 0.0.31 or later. There are three critical vulnerabilities with PoC exploits, so attackers will start pushing out malicious payloads. Also, consider using safer serialization formats like Safetensors instead of Pickle for your ML models.**
#cybersecurity #infosec #advisory #vulnerability
https://beyondmachines.net/event_details/critical-vulnerabilities-reported-in-picklescan-z-j-b-t-s/gD2P6Ple2L
updated 2025-09-18T12:51:23
3 posts
This affects CVE-2025-10155, CVE-2025-10156, and CVE-2025-10157.
JFrog, from yesterday: PyTorch Users at Risk: Unveiling 3 Zero-Day PickleScan Vulnerabilities https://jfrog.com/blog/unveiling-3-zero-day-vulnerabilities-in-picklescan/
More:
Infosecurity-Magazine: Critical PickleScan Vulnerabilities Expose AI Model Supply Chains https://www.infosecurity-magazine.com/news/picklescan-flaws-expose-ai-supply/ #infosec #opensource #Python #zeroday
##This affects CVE-2025-10155, CVE-2025-10156, and CVE-2025-10157.
JFrog, from yesterday: PyTorch Users at Risk: Unveiling 3 Zero-Day PickleScan Vulnerabilities https://jfrog.com/blog/unveiling-3-zero-day-vulnerabilities-in-picklescan/
More:
Infosecurity-Magazine: Critical PickleScan Vulnerabilities Expose AI Model Supply Chains https://www.infosecurity-magazine.com/news/picklescan-flaws-expose-ai-supply/ #infosec #opensource #Python #zeroday
##Critical vulnerabilities reported in PickleScan
The JFrog Security Research Team discovered three critical zero-day vulnerabilities (CVE-2025-10155, CVE-2025-10156, CVE-2025-10157) in PickleScan, a widely used ML model security scanning tool, that allow attackers to completely bypass malware detection through file extension manipulation, corrupted ZIP archives, and blacklist evasion techniques. These vulnerabilities could enable large-scale supply chain attacks by distributing malicious ML models through platforms like Hugging Face.
**If you use PickleScan to scan machine learning models, update ASAP to version 0.0.31 or later. There are three critical vulnerabilities with PoC exploits, so attackers will start pushing out malicious payloads. Also, consider using safer serialization formats like Safetensors instead of Pickle for your ML models.**
#cybersecurity #infosec #advisory #vulnerability
https://beyondmachines.net/event_details/critical-vulnerabilities-reported-in-picklescan-z-j-b-t-s/gD2P6Ple2L
updated 2025-09-16T12:49:16.060000
4 posts
86 repos
https://github.com/clevernyyyy/CVE-2025-55182-Dockerized
https://github.com/emadshanab/POC-for-CVE-2025-55182
https://github.com/alexandre-briongos-wavestone/react-cve-2025-55182-lab
https://github.com/Chocapikk/CVE-2025-55182
https://github.com/ZemarKhos/CVE-2025-55182-Exploit-PoC-Scanner
https://github.com/atastycookie/CVE-2025-55182
https://github.com/ducducuc111/CVE-2025-55182-poc
https://github.com/Chelsea486MHz/CVE-2025-55182-test
https://github.com/BankkRoll/Quickcheck-CVE-2025-55182-React-and-CVE-2025-66478-Next.js
https://github.com/ps-interactive/cve-2025-55182
https://github.com/Airis101/CVE-2025-55182-analysis
https://github.com/lunbun/CVE-2025-55188
https://github.com/Ashwesker/Blackash-CVE-2025-55182
https://github.com/c0rydoras/CVE-2025-55182
https://github.com/hoosin/CVE-2025-55182
https://github.com/im-hanzou/CVE-2025-55182-POC-SCANNER
https://github.com/nehkark/CVE-2025-55182
https://github.com/Rat5ak/CVE-2025-55182-React2Shell-RCE-POC
https://github.com/Sotatek-KhaiNguyen3/CVE-2025-55182
https://github.com/SoICT-BKSEC/CVE-2025-55182-docker-lab
https://github.com/GarethMSheldon/React2Shell-CVE-2025-55182-Detector
https://github.com/younesZdDz/CVE-2025-55182
https://github.com/Rsatan/CVE-2025-55182-Tools
https://github.com/heiheishushu/rsc_detect_CVE-2025-55182
https://github.com/lachlan2k/React2Shell-CVE-2025-55182-original-poc
https://github.com/ngvcanh/CVE-2025-55182-Attack-Analysis
https://github.com/sudo-Yangziran/CVE-2025-55182POC
https://github.com/zessu/CVE-2025-55182-Typescript
https://github.com/sherlocksecurity/CVE-2025-55182-Exploit-scanner
https://github.com/Pa2sw0rd/exploit-CVE-2025-55182-poc
https://github.com/ceortiz33/CVE-2025-55182
https://github.com/selectarget/CVE-2025-55182-Exploit
https://github.com/hzhsec/cve_2025_55182_test
https://github.com/ZihxS/check-react-rce-cve-2025-55182
https://github.com/nomorebreach/POC-CVE-2025-55182
https://github.com/whiteov3rflow/CVE-2025-55182-poc
https://github.com/Spritualkb/CVE-2025-55182-exp
https://github.com/f0xyx/CVE-2025-55182-Scanner
https://github.com/santihabib/CVE-2025-55182-analysis
https://github.com/aliclub0x00/CVE-2025-55182-POC-NEXTJS
https://github.com/XiaomingX/CVE-2025-55182-poc
https://github.com/EynaExp/CVE-2025-55182-POC
https://github.com/ejpir/CVE-2025-55182-research
https://github.com/jf0x3a/CVE-2025-55182-exploit
https://github.com/prestonhashworth/cve-2025-55182
https://github.com/nanwinata/CVE-2025-55182-Scanner
https://github.com/oways/React2shell-CVE-2025-55182-checker
https://github.com/hualy13/CVE-2025-55182
https://github.com/aquinn-r7/CVE-2025-55182-VulnCheckPOC
https://github.com/nerium-security/CVE-2025-55182
https://github.com/ThemeHackers/CVE-2025-55182
https://github.com/logesh-GIT001/CVE-2025-55182
https://github.com/l4rm4nd/CVE-2025-55182
https://github.com/xkillbit/cve-2025-55182-scanner
https://github.com/joshterrill/CVE-2025-55182-realistic-poc
https://github.com/ABCFabian/React2Shell-CVE-2025-55182-Testing-Environment
https://github.com/fatguru/CVE-2025-55182-scanner
https://github.com/RuoJi6/CVE-2025-55182-RCE-shell
https://github.com/carlosaruy/CVE-2025-55182
https://github.com/tlfyyds/cve-2025-55182-getshell
https://github.com/topstar88/CVE-2025-55182
https://github.com/mingyisecurity-lab/CVE-2025-55182-TOOLS
https://github.com/dissy123/cve-2025-55182
https://github.com/RajChowdhury240/React2Shell-CVE-2025-55182
https://github.com/acheong08/CVE-2025-55182-poc
https://github.com/aspen-labs/CVE-2025-55182-checker
https://github.com/MedusaSH/POC-CVE-2025-55182
https://github.com/dwisiswant0/CVE-2025-55182
https://github.com/Cillian-Collins/CVE-2025-55182
https://github.com/0xPThree/cve-2025-55182
https://github.com/m3m0ryc0rrupt/CVE-2025-55182-PoC
https://github.com/hunters-sec/CVE-2025-55188-7z-exploit
https://github.com/sickwell/CVE-2025-55182
https://github.com/MrR0b0t19/CVE-2025-55182-shellinteractive
https://github.com/rl0x01/CVE-2025-55182_PoC
https://github.com/kk12-30/CVE-2025-55182
https://github.com/Golden-Secure/CVE-2025-55182
https://github.com/Saturate/CVE-2025-55182-Scanner
https://github.com/zzhorc/CVE-2025-55182
https://github.com/msanft/CVE-2025-55182
https://github.com/TH-SecForge/CVE-2025-55182
https://github.com/songsanggggg/CVE-2025-55182
https://github.com/onlylovetx/CVE-2025-55182-CVE-2025-66478-Exploit-GUI
https://github.com/Pizz33/CVE-2025-55182-burpscanner
https://github.com/pax-k/react2shell-CVE-2025-55182-full-rce-script
To be clear, there are no public PoCs of yesterday's React vulnerability (CVE-2025-55182). The one that was being claimed as a POC has been outed as slop. Indeed, they even renamed the repo.
https://github.com/ejpir/CVE-2025-55182-research
The first PoCs for these vulns are now always fake.
Watch https://react2shell.com for disclosure from the discoverers.
##Today in "AI ruins everything": AI generated "PoC" for the React RCE CVE-2025-55182, wasting countless defenders' hours, now get included in the CVE references. 🤦♂️
At least the co-author alongside the AI has updated the README now:
https://github.com/ejpir/CVE-2025-55182-poc
Looks like the original reporter plans on posting more details at some point in the future here:
https://react2shell.com/
To be clear, there are no public PoCs of yesterday's React vulnerability (CVE-2025-55182). The one that was being claimed as a POC has been outed as slop. Indeed, they even renamed the repo.
https://github.com/ejpir/CVE-2025-55182-research
The first PoCs for these vulns are now always fake.
Watch https://react2shell.com for disclosure from the discoverers.
##Today in "AI ruins everything": AI generated "PoC" for the React RCE CVE-2025-55182, wasting countless defenders' hours, now get included in the CVE references. 🤦♂️
At least the co-author alongside the AI has updated the README now:
https://github.com/ejpir/CVE-2025-55182-poc
Looks like the original reporter plans on posting more details at some point in the future here:
https://react2shell.com/
updated 2025-04-24T21:41:24
2 posts
24 repos
https://github.com/LOURC0D3/CVE-2024-4367-PoC
https://github.com/kabiri-labs/CVE-2024-4367-PoC
https://github.com/PenguinCabinet/CVE-2024-4367-hands-on
https://github.com/Zombie-Kaiser/cve-2024-4367-PoC-fixed
https://github.com/Bhavyakcwestern/Hacking-pdf.js-vulnerability
https://github.com/VVeakee/CVE-2024-4367
https://github.com/snyk-labs/pdfjs-vuln-demo
https://github.com/1337rokudenashi/Odoo_PDFjs_CVE-2024-4367.pdf
https://github.com/avalahEE/pdfjs_disable_eval
https://github.com/BektiHandoyo/cve-pdf-host
https://github.com/s4vvysec/CVE-2024-4367-POC
https://github.com/clarkio/pdfjs-vuln-demo
https://github.com/0xr2r/CVE-2024-4367
https://github.com/Scivous/CVE-2024-4367-npm
https://github.com/pedrochalegre7/CVE-2024-4367-pdf-sample
https://github.com/spaceraccoon/detect-cve-2024-4367
https://github.com/UnHackerEnCapital/PDFernetRemotelo
https://github.com/Masamuneee/CVE-2024-4367-Analysis
https://github.com/exfil0/WEAPONIZING-CVE-2024-4367
https://github.com/MihranGIT/POC_CVE-2024-4367
https://github.com/MihranGIT/CVE-2024-4367
https://github.com/elamani-drawing/CVE-2024-4367-POC-PDFJS
🚨Nextcloud was vulnerable to XSS in PDF.js (CVE-2024-4367) found by Thomas Rinsma at CodeanIO.
Although Nextcloud mitigated the vulnerability in their portal by disabling eval, the viewer.html component of the vulnerable PDF.js was still exposed.
https://www.redteam-pentesting.de/en/advisories/rt-sa-2025-003/
##🚨Nextcloud was vulnerable to XSS in PDF.js (CVE-2024-4367) found by Thomas Rinsma at CodeanIO.
Although Nextcloud mitigated the vulnerability in their portal by disabling eval, the viewer.html component of the vulnerable PDF.js was still exposed.
https://www.redteam-pentesting.de/en/advisories/rt-sa-2025-003/
##updated 2024-11-21T05:47:48.830000
2 posts
Good introduction to a blog post. I came to it by chance after finishing the work today, relaxing a bit after auditing a state machine, but not as complex as Array.prototype.concat implementation, for sure.
A Bug's Life: CVE-2021-21225
https://tiszka.com/blog/CVE_2021_21225.html
Good introduction to a blog post. I came to it by chance after finishing the work today, relaxing a bit after auditing a state machine, but not as complex as Array.prototype.concat implementation, for sure.
A Bug's Life: CVE-2021-21225
https://tiszka.com/blog/CVE_2021_21225.html
updated 2023-01-28T05:05:39
2 posts
And there's F5 again. Publishing impact to some of their shit by CVE-2019-8457. Yes, that CVE was published on 30 May 2019 and F5 is just now publishing an advisory for it. And there is impact.
##And there's F5 again. Publishing impact to some of their shit by CVE-2019-8457. Yes, that CVE was published on 30 May 2019 and F5 is just now publishing an advisory for it. And there is impact.
##Sicherheitslücke: OpenAI Codex CLI führt versteckte Befehle aus Repository-Dateien aus
Die unter CVE-2025-61260 geführte Lücke ermöglicht es Angreifern, über manipulierte Repository-Dateien beliebigen Code auf Entwicklersystemen auszuführen – ganz ohne Wissen oder Zustimmung der Nutzer.
##📢 CVE-2025-61260 : injection de commandes dans OpenAI Codex CLI via configuration locale de projet
📝 Source et contexte — Check Point Research publie une analyse détaillant CVE-2025-61260, une...
📖 cyberveille : https://cyberveille.ch/posts/2025-12-03-cve-2025-61260-injection-de-commandes-dans-openai-codex-cli-via-configuration-locale-de-projet/
🌐 source : https://research.checkpoint.com/2025/openai-codex-cli-command-injection-vulnerability/
#CVE_2025_61260 #IOC #Cyberveille
Sicherheitslücke: OpenAI Codex CLI führt versteckte Befehle aus Repository-Dateien aus
Die unter CVE-2025-61260 geführte Lücke ermöglicht es Angreifern, über manipulierte Repository-Dateien beliebigen Code auf Entwicklersystemen auszuführen – ganz ohne Wissen oder Zustimmung der Nutzer.
##Command injection flaw in OpenAI Codex CLI enables silent remote code execution
Security researchers discovered CVE-2025-61260, a command injection vulnerability in OpenAI Codex CLI that allows attackers to achieve arbitrary code execution by placing malicious .env and configuration files in repositories, which the tool automatically executes without user approval when developers run the codex command.
**If you use OpenAI Codex CLI, update to version 0.23.0 or later. Your Codex CLI (and your computer running it) can be hacked by a simple malicious repo file you just cloned Until updated, don't run codex in unfamiliar repositories, and always check .env files and .codex configuration folders for suspicious commands before running the tool.**
#cybersecurity #infosec #advisory #vulnerability
https://beyondmachines.net/event_details/command-injection-flaw-in-openai-codex-cli-enables-silent-remote-code-execution-8-g-e-z-9/gD2P6Ple2L
🚨 CVE-2025-66489: CRITICAL bug in cal.com (<5.9.8) lets attackers bypass password checks with valid TOTP, risking account compromise. Patch to 5.9.8+ ASAP! Details: https://radar.offseq.com/threat/cve-2025-66489-cwe-303-incorrect-implementation-of-10655bf9 #OffSeq #calcom #vuln #CVE202566489 #infosec
##CISA has added two Android Framework 0-days (CVE-2025-48572 & CVE-2025-48633) to the KEV list, confirming active exploitation.
Together, they enable privilege escalation and information disclosure, forming a potentially complete compromise path for targeted devices.
Federal agencies have a December 23 patch deadline, and wider organizations are encouraged to roll out updates and monitor for related indicators.
💬 Mobile ecosystems remain a critical attack surface - what best practices have worked for your teams?
Source: https://cybersecuritynews.com/android-0-day-vulnerability-exploited/
Follow us for ongoing vulnerability and threat intelligence updates.
#Cybersecurity #AndroidSecurity #KEV #CISA #ZeroDay #MobileThreats #ThreatIntel #Infosec #SecurityUpdates #DeviceSecurity
##CISA has added two Android Framework 0-days (CVE-2025-48572 & CVE-2025-48633) to the KEV list, confirming active exploitation.
Together, they enable privilege escalation and information disclosure, forming a potentially complete compromise path for targeted devices.
Federal agencies have a December 23 patch deadline, and wider organizations are encouraged to roll out updates and monitor for related indicators.
💬 Mobile ecosystems remain a critical attack surface - what best practices have worked for your teams?
Source: https://cybersecuritynews.com/android-0-day-vulnerability-exploited/
Follow us for ongoing vulnerability and threat intelligence updates.
#Cybersecurity #AndroidSecurity #KEV #CISA #ZeroDay #MobileThreats #ThreatIntel #Infosec #SecurityUpdates #DeviceSecurity
##CISA has added two vulnerabilities to the KEV Catalog:
CVE-2025-48633: Android Framework Information Disclosure Vulnerability
CVE-2025-48572: Android Framework Privilege Escalation Vulnerability
##CVE ID: CVE-2025-48633
Vendor: Android
Product: Framework
Date Added: 2025-12-02
Notes: https://source.android.com/docs/security/bulletin/2025-12-01 ; https://nvd.nist.gov/vuln/detail/CVE-2025-48633
CVE URL: https://nvd.nist.gov/vuln/detail/CVE-2025-48633
CISA has updated the KEV catalogue.
- CVE-2025-48572: Android Framework Privilege Escalation Vulnerability https://www.cve.org/CVERecord?id=CVE-2025-48572
- CVE-2025-48633: Android Framework Information Disclosure Vulnerability https://www.cve.org/CVERecord?id=CVE-2025-48633
Also:
CISA Releases Five Industrial Control Systems Advisories https://www.cisa.gov/news-events/alerts/2025/12/02/cisa-releases-five-industrial-control-systems-advisories #CISA #infosec #Android #Google #vulnerability
##CISA has added two Android Framework 0-days (CVE-2025-48572 & CVE-2025-48633) to the KEV list, confirming active exploitation.
Together, they enable privilege escalation and information disclosure, forming a potentially complete compromise path for targeted devices.
Federal agencies have a December 23 patch deadline, and wider organizations are encouraged to roll out updates and monitor for related indicators.
💬 Mobile ecosystems remain a critical attack surface - what best practices have worked for your teams?
Source: https://cybersecuritynews.com/android-0-day-vulnerability-exploited/
Follow us for ongoing vulnerability and threat intelligence updates.
#Cybersecurity #AndroidSecurity #KEV #CISA #ZeroDay #MobileThreats #ThreatIntel #Infosec #SecurityUpdates #DeviceSecurity
##CISA has added two Android Framework 0-days (CVE-2025-48572 & CVE-2025-48633) to the KEV list, confirming active exploitation.
Together, they enable privilege escalation and information disclosure, forming a potentially complete compromise path for targeted devices.
Federal agencies have a December 23 patch deadline, and wider organizations are encouraged to roll out updates and monitor for related indicators.
💬 Mobile ecosystems remain a critical attack surface - what best practices have worked for your teams?
Source: https://cybersecuritynews.com/android-0-day-vulnerability-exploited/
Follow us for ongoing vulnerability and threat intelligence updates.
#Cybersecurity #AndroidSecurity #KEV #CISA #ZeroDay #MobileThreats #ThreatIntel #Infosec #SecurityUpdates #DeviceSecurity
##CISA has added two vulnerabilities to the KEV Catalog:
CVE-2025-48633: Android Framework Information Disclosure Vulnerability
CVE-2025-48572: Android Framework Privilege Escalation Vulnerability
##CVE ID: CVE-2025-48572
Vendor: Android
Product: Framework
Date Added: 2025-12-02
Notes: https://source.android.com/docs/security/bulletin/2025-12-01 ; https://nvd.nist.gov/vuln/detail/CVE-2025-48572
CVE URL: https://nvd.nist.gov/vuln/detail/CVE-2025-48572
CISA has updated the KEV catalogue.
- CVE-2025-48572: Android Framework Privilege Escalation Vulnerability https://www.cve.org/CVERecord?id=CVE-2025-48572
- CVE-2025-48633: Android Framework Information Disclosure Vulnerability https://www.cve.org/CVERecord?id=CVE-2025-48633
Also:
CISA Releases Five Industrial Control Systems Advisories https://www.cisa.gov/news-events/alerts/2025/12/02/cisa-releases-five-industrial-control-systems-advisories #CISA #infosec #Android #Google #vulnerability
##