[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"landing-trending":3,"cve-CVE-2019-5302":30,"landing-articles":257},{"count":4,"next":5,"previous":6,"results":7},266,"http:\u002F\u002Fweb:8606\u002Fapi\u002Ftrending_attacks\u002F?page=2&page_size=3&sorted_by=-published_at",null,[8,17,20],{"id":9,"title":10,"summary":11,"published_at":12,"severity":13,"vendor":14,"products":15},265,"Google Brotli decoder - Remote Code Execution via compressed requests (Exploitation Check)","This control is the second step of the Patrowl response to CVE-2026-111497 (Node2Shell). It complements the first control of 22 October 2026, which focused on the Node.js runtime, and does not replace it.\r\n\r\nWhy a second control\r\n\r\nCVE-2026-111497 is an out-of-bounds write in the Google Brotli decoder, the library that decompresses Brotli (\"br\") data. It was first published as a Node.js vulnerability, because Node.js bundles this decoder. Later publications showed that the flaw is in the library itself. Every product that embeds an affected version of the decoder is concerned, whatever its language or vendor. A public proof of concept demonstrates code execution.\r\n\r\nAny server that decompresses request bodies sent with \"Content-Encoding: br\" exposes the decoder to unauthenticated attackers. Known cases include Express 5 and NestJS 11 on Node.js, Koa and Fastify setups, Bun, Envoy and Istio with request decompression enabled, and any application or reverse proxy that decodes Brotli request bodies with an affected library.\r\n\r\nThe flaw also works in the other direction. A malicious server can compromise an unpatched client that decodes a Brotli response, for example Node.js fetch(), Python clients (requests, httpx, aiohttp, Scrapy) with the Brotli or brotlicffi package, or libcurl builds with Brotli support.\r\n\r\nWhat this control checks\r\n\r\nPatrowl sends small, valid Brotli-compressed requests to each asset and observes whether the server decodes them. The check does not depend on the technology: it detects the behaviour, whatever the stack behind it. These requests are what any legitimate client could send. They never reach the vulnerable code path and cannot affect the availability of the service.\r\n\r\nHow to read the result\r\n\r\nPotentially impacted means the asset decodes Brotli request bodies: the attack surface is exposed. It does not confirm that the asset is vulnerable. The version of the Brotli decoder in use is not visible from the outside.\r\n\r\nThis check covers applications that parse request bodies on their root path. A Not impacted result does not rule out exposure on other routes, nor on the client side. Checking the versions on the servers remains the only exhaustive verification.\r\n\r\nAffected and fixed versions\r\n\r\nGoogle Brotli 1.0.3 to 1.2.0 are affected, fixed in 1.0.10, 1.1.1 and 1.2.1. Fixed releases of the main products embedding it: Node.js 22.23.4, 24.22.1 and 26.12.1 (end-of-life lines 20.x and older and 25.x receive no fix), Bun 1.4.4, Envoy 1.37.8, 1.38.6, 1.39.3 and 1.40.0, Istio 1.29.9, 1.30.6 and 1.31.2, Python Brotli 1.2.1 and brotlicffi 1.2.1.0. Products that link against the system library depend on the Brotli package of the Linux distribution.\r\n\r\nRecommendations\r\n\r\nUpdate every component that embeds the Brotli decoder (only real fix). Start with the assets flagged by this control. Restart the processes after the update. Rebuild containers, single-executable applications and appliances that bundle an affected runtime or library.\r\n\r\nReduce the exposure until the update is deployed. Reject requests with \"Content-Encoding: br\" at the reverse proxy, load balancer or WAF, case-insensitively and including lists such as \"gzip, br\". On Envoy and Istio, disable request decompression for Brotli.\r\n\r\nReview outbound calls. List the features that fetch content from servers you do not control, and patch the services that host them first.","2026-10-24T10:37:22.192753Z",4,"google",[16],"brotli",{"id":4,"title":10,"summary":18,"published_at":12,"severity":13,"vendor":14,"products":19},"This control is the second step of the Patrowl response to CVE-2026-111497 (Node2Shell). It complements the first control of 22 October 2026, which focused on the Node.js runtime, and does not replace it.\r\n\r\nWhy a second control\r\n\r\nCVE-2026-111497 is an out-of-bounds write in the Google Brotli decoder, the library that decompresses Brotli (\"br\") data. It was first published as a Node.js vulnerability, because Node.js bundles this decoder. Later publications showed that the flaw is in the library itself. Every product that embeds an affected version of the decoder is concerned, whatever its language or vendor. A public proof of concept demonstrates code execution.\r\n\r\nAny server that decompresses request bodies sent with \"Content-Encoding: br\" exposes the decoder to unauthenticated attackers. Known cases include Express 5 and NestJS 11 on Node.js, Koa and Fastify setups, Bun, Envoy and Istio with request decompression enabled, and any application or reverse proxy that decodes Brotli request bodies with an affected library.\r\n\r\nThe flaw also works in the other direction. A malicious server can compromise an unpatched client that decodes a Brotli response, for example Node.js fetch(), Python clients (requests, httpx, aiohttp, Scrapy) with the Brotli or brotlicffi package, or libcurl builds with Brotli support.\r\n\r\nWhat this control checks\r\n\r\nPatrowl sends small, valid Brotli-compressed requests to each asset and observes whether the server decodes them. The check does not depend on the technology: it detects the behaviour, whatever the stack behind it. These requests are what any legitimate client could send. They never reach the vulnerable code path and cannot affect the availability of the service.\r\n\r\nHow to read the result\r\n\r\nPotentially impacted means the asset decodes Brotli request bodies: the attack surface is exposed. It does not confirm that the asset is vulnerable. The version of the Brotli decoder in use is not visible from the outside.\r\n\r\nThis check covers applications that parse request bodies on their root path. A Not impacted result does not rule out exposure on other routes, nor on the client side. Checking the versions on the servers remains the only exhaustive verification.\r\n\r\nTwo situations are possible. When the decoding is done by your own application or reverse proxy, identify the component and update it. If an update is not possible right away, reject requests with \"Content-Encoding: br\" at the reverse proxy or WAF.\r\n\r\nWhen the asset is hosted on a managed platform or behind a CDN (for example Platform.sh, Upsun or Fastly), the decoding may be done by the provider's edge router, in front of your application. You cannot patch it yourself, but this router handles all the traffic of your site. Ask your provider to confirm that its edge components are patched against CVE-2026-111497. Assets hosted on a managed platform or behind a CDN carry the tag \"paas: platform.sh\" or \"cdn: fastly\" in the asset view: for these assets, the Brotli decoding is done by the provider's edge router, in front of your application, and only the provider can patch it.\r\n\r\nAffected and fixed versions\r\n\r\nGoogle Brotli 1.0.3 to 1.2.0 are affected, fixed in 1.0.10, 1.1.1 and 1.2.1. Fixed releases of the main products embedding it: Node.js 22.23.4, 24.22.1 and 26.12.1 (end-of-life lines 20.x and older and 25.x receive no fix), Bun 1.4.4, Envoy 1.37.8, 1.38.6, 1.39.3 and 1.40.0, Istio 1.29.9, 1.30.6 and 1.31.2, Python Brotli 1.2.1 and brotlicffi 1.2.1.0. Products that link against the system library depend on the Brotli package of the Linux distribution.\r\n\r\nRecommendations\r\n\r\nUpdate every component that embeds the Brotli decoder (only real fix). Start with the assets flagged by this control. Restart the processes after the update. Rebuild containers, single-executable applications and appliances that bundle an affected runtime or library.\r\n\r\nReduce the exposure until the update is deployed. Reject requests with \"Content-Encoding: br\" at the reverse proxy, load balancer or WAF, case-insensitively and including lists such as \"gzip, br\". On Envoy and Istio, disable request decompression for Brotli.\r\n\r\nContact your edge provider about the status of the pathing (Fastly \u002F Plateform.sh)\r\n\r\nReview outbound calls. List the features that fetch content from servers you do not control, and patch the services that host them first.",[16],{"id":21,"title":22,"summary":23,"published_at":24,"severity":13,"vendor":25,"products":26},263,"Oracle Java SE JSSE - Improper Access Control & Unauthorized Data Access & Unauthorized Data Modification","Oracle Java SE is the Java runtime and development platform. Its JSSE (Java Secure Socket Extension) component provides TLS\u002FSSL for secure network communication. Oracle GraalVM is a JDK distribution based on the same platform.\r\n\r\nCVE-2026-91403\r\n\r\nA vulnerability in the JSSE component of Oracle Java SE, Oracle GraalVM for JDK and Oracle GraalVM Enterprise Edition can be exploited by an unauthenticated attacker with network access over multiple protocols. A successful attack can give unauthorized access to critical data and allow unauthorized creation, deletion or modification of data. It can also affect sandboxed Java Web Start applications and applets that run untrusted code. The record lists the weakness as CWE-284 (Improper Access Control) in the CISA ADP entry, while another database lists CWE-295. The record lists these affected versions:\r\n- Oracle Java SE: 8u511, 8u511-perf, 11.0.33, 17.0.21, 21.0.13, 25.0.5, 27.0.1.\r\n- Oracle GraalVM for JDK: 17.0.21, 21.0.13.\r\n- Oracle GraalVM Enterprise Edition: 21.3.20.\r\n\r\nOracle published an out-of-cycle Security Alert on October 21, 2026. One secondary source says the fix makes Java distrust eight compromised intermediate CA certificates shipped with the JDK. The Oracle-focused sources do not confirm this root cause, so check it against the Oracle advisory. CISA ADP SSVC data shows Exploitation: none, Automatable: yes, Technical Impact: total. The CVE is not in the CISA KEV catalog as of October 22, 2026, and its EPSS score is below 1%.","2026-10-23T14:12:32.871954Z","Oracle",[27,28,29],"Oracle Java SE","Oracle GraalVM Enterprise Edition","Oracle GraalVM for JDK",{"id":31,"cve_id":32,"euvd_id":33,"summary":34,"published":35,"cvss_data":36,"is_remote":51,"cwes":52,"cpes":54,"technologies":149,"references":244,"score":246,"epss_score":247,"epss_percentile":248,"is_kev":51,"cisa_kev_date_added":6,"cisa_kev_due_date":6,"cisa_ssvc":249,"attack_mappings":255,"exploits":256},235096,"CVE-2019-5302","EUVD-2019-14907","There are two denial of service vulnerabilities on some Huawei smartphones. An attacker may send specially crafted TD-SCDMA messages from a rogue base station to the affected devices. Due to insufficient input validation of two values when parsing the messages, successful exploit may cause device abnormal. This is 1 out of 2 vulnerabilities. Different than CVE-2020-5303. Affected products are: ALP-AL00B: earlier than 9.1.0.333(C00E333R2P1T8) ALP-L09: earlier than 9.1.0.300(C432E4R1P9T8) ALP-L29: earlier than 9.1.0.315(C636E5R1P13T8) BLA-L29C: earlier than 9.1.0.321(C636E4R1P14T8), earlier than 9.1.0.330(C432E6R1P12T8), earlier than 9.1.0.302(C635E4R1P13T8) Berkeley-AL20: earlier than 9.1.0.333(C00E333R2P1T8) Berkeley-L09: earlier than 9.1.0.350(C10E3R1P14T8), earlier than 9.1.0.351(C432E5R1P13T8), earlier than 9.1.0.350(C636E4R1P13T8) Charlotte-L09C: earlier than 9.1.0.311(C185E4R1P11T8), earlier than 9.1.0.345(C432E8R1P11T8) Charlotte-L29C: earlier than 9.1.0.325(C185E4R1P11T8), earlier than 9.1.0.335(C636E3R1P13T8), earlier than 9.1.0.345(C432E8R1P11T8), earlier than 9.1.0.336(C605E3R1P12T8) Columbia-AL10B: earlier than 9.1.0.333(C00E333R1P1T8) Columbia-L29D: earlier than 9.1.0.350(C461E3R1P11T8), earlier than 9.1.0.350(C185E3R1P12T8), earlier than 9.1.0.350(C10E5R1P14T8), earlier than 9.1.0.351(C432E5R1P13T8) Cornell-AL00A: earlier than 9.1.0.333(C00E333R1P1T8) Cornell-L29A: earlier than 9.1.0.328(C185E1R1P9T8), earlier than 9.1.0.328(C432E1R1P9T8), earlier than 9.1.0.330(C461E1R1P9T8), earlier than 9.1.0.328(C636E2R1P12T8) Emily-L09C: earlier than 9.1.0.336(C605E4R1P12T8), earlier than 9.1.0.311(C185E2R1P12T8), earlier than 9.1.0.345(C432E10R1P12T8) Emily-L29C: earlier than 9.1.0.311(C605E2R1P12T8), earlier than 9.1.0.311(C636E7R1P13T8), earlier than 9.1.0.311(C432E7R1P11T8) Ever-L29B: earlier than 9.1.0.311(C185E3R3P1), earlier than 9.1.0.310(C636E3R2P1), earlier than 9.1.0.310(C432E3R1P12) HUAWEI Mate 20: earlier than 9.1.0.131(C00E131R3P1) HUAWEI Mate 20 Pro: earlier than 9.1.0.310(C185E10R2P1) HUAWEI Mate 20 RS: earlier than 9.1.0.135(C786E133R3P1) HUAWEI Mate 20 X: earlier than 9.1.0.135(C00E133R2P1) HUAWEI P20: earlier than 9.1.0.333(C00E333R1P1T8) HUAWEI P20 Pro: earlier than 9.1.0.333(C00E333R1P1T8) HUAWEI P30: earlier than 9.1.0.193 HUAWEI P30 Pro: earlier than 9.1.0.186(C00E180R2P1) HUAWEI Y9 2019: earlier than 9.1.0.220(C605E3R1P1T8) HUAWEI nova lite 3: earlier than 9.1.0.305(C635E8R2P2) Honor 10 Lite: earlier than 9.1.0.283(C605E8R2P2) Honor 8X: earlier than 9.1.0.221(C461E2R1P1T8) Honor View 20: earlier than 9.1.0.238(C432E1R3P1) Jackman-L22: earlier than 9.1.0.247(C636E2R4P1T8) Paris-L21B: earlier than 9.1.0.331(C432E1R1P2T8) Paris-L21MEB: earlier than 9.1.0.331(C185E4R1P3T8) Paris-L29B: earlier than 9.1.0.331(C636E1R1P3T8) Sydney-AL00: earlier than 9.1.0.212(C00E62R1P7T8) Sydney-L21: earlier than 9.1.0.215(C432E1R1P1T8), earlier than 9.1.0.213(C185E1R1P1T8) Sydney-L21BR: earlier than 9.1.0.213(C185E1R1P2T8) Sydney-L22: earlier than 9.1.0.258(C636E1R1P1T8) Sydney-L22BR: earlier than 9.1.0.258(C636E1R1P1T8) SydneyM-AL00: earlier than 9.1.0.228(C00E78R1P7T8) SydneyM-L01: earlier than 9.1.0.215(C782E2R1P1T8), earlier than 9.1.0.213(C185E1R1P1T8), earlier than 9.1.0.270(C432E3R1P1T8) SydneyM-L03: earlier than 9.1.0.217(C605E1R1P1T8) SydneyM-L21: earlier than 9.1.0.221(C461E1R1P1T8), earlier than 9.1.0.215(C432E4R1P1T8) SydneyM-L22: earlier than 9.1.0.259(C185E1R1P2T8), earlier than 9.1.0.220(C635E1R1P2T8), earlier than 9.1.0.216(C569E1R1P1T8) SydneyM-L23: earlier than 9.1.0.226(C605E2R1P1T8) Yale-L21A: earlier than 9.1.0.154(C432E2R3P2), earlier than 9.1.0.154(C461E2R2P1), earlier than 9.1.0.154(C636E2R2P1) Honor 20: earlier than 9.1.0.152(C00E150R5P1) Honor Magic2: earlier than 10.0.0.187 Honor V20: earlier than 9.1.0.234(C00E234R4P3)","2020-04-27T20:15:00Z",{"cvss_v2.0":37,"cvss_v3.1":45},{"version":38,"baseScore":39,"accessVector":40,"vectorString":41,"authentication":42,"integrityImpact":42,"accessComplexity":43,"availabilityImpact":44,"confidentialityImpact":42},"2.0",2.9,"ADJACENT_NETWORK","AV:A\u002FAC:M\u002FAu:N\u002FC:N\u002FI:N\u002FA:P","NONE","MEDIUM","PARTIAL",{"scope":46,"version":47,"baseScore":48,"attackVector":40,"baseSeverity":43,"vectorString":49,"integrityImpact":42,"userInteraction":42,"attackComplexity":50,"availabilityImpact":50,"privilegesRequired":42,"confidentialityImpact":42},"UNCHANGED","3.1",5.3,"CVSS:3.1\u002FAV:A\u002FAC:H\u002FPR:N\u002FUI:N\u002FS:U\u002FC:N\u002FI:N\u002FA:H","HIGH",false,[53],"CWE-20",[55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148],"cpe:2.3:o:huawei:ever-l29b_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:bla-l29c:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:alp-l29_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:p20:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:honor_10_lite:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:emily-l29c:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:columbia-l29d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:honor_20:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:paris-l21b:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:charlotte-l09c:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:p20_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:honor_view_20:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:p30:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:yale-l21a_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:sydneym-al00:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:sydney-l22_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:paris-l21meb:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:columbia-al10b_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:p30_pro:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:charlotte-l09c_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:yale-l21a:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:jackman-l22:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:mate_20_pro:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:paris-l21b_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:cornell-l29a:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:berkeley-al20_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:cornell-al00a:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:sydneym-al00_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:bla-l29c_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:y9_2019_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:sydneym-l22:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:alp-l29:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:p30_pro_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:mate_20_x:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:p20_pro_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:p30_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:sydney-l22:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:alp-l09_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:honor_10_lite_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:nova_lite_3_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:columbia-l29d:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:paris-l29b:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:sydneym-l21_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:mate_20_x_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:mate_20_rs:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:sydneym-l23:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:y9_2019:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:sydneym-l03_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:sydneym-l23_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:honor_magic2:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:alp-al00b:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:mate_20:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:berkeley-l09:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:emily-l09c_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:honor_v20:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:sydney-l21:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:columbia-al10b:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:emily-l09c:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:sydney-al00_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:jackman-l22_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:cornell-al00a_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:honor_8x_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:sydney-l22br:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:sydney-l21br_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:sydney-l22br_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:honor_8x:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:honor_20_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:mate_20_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:cornell-l29a_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:sydneym-l21:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:alp-l09:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:ever-l29b:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:mate_20_pro_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:sydneym-l01:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:emily-l29c_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:p20_pro:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:mate_20_rs_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:paris-l21meb_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:sydney-al00:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:alp-al00b_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:nova_lite_3:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:charlotte-l29c_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:honor_magic2_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:charlotte-l29c:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:sydneym-l22_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:sydney-l21_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:honor_view_20_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:sydneym-l01_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:berkeley-l09_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:sydney-l21br:-:*:*:*:*:*:*:*","cpe:2.3:o:huawei:paris-l29b_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:huawei:honor_v20_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:huawei:berkeley-al20:-:*:*:*:*:*:*:*","cpe:2.3:h:huawei:sydneym-l03:-:*:*:*:*:*:*:*",[150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,228,229,230,231,232,233,234,235,236,237,238,239,240,241,242,243],"Huawei Paris-L29B Firmware","Huawei Cornell-L29A Firmware","Huawei Berkeley-Al20 Firmware","Huawei Sydney-L22Br Firmware","Huawei Paris-L21B Firmware","Huawei P30 Pro","Huawei Sydneym-Al00","Huawei Honor 10 Lite","Huawei Mate 20","Huawei Ever-L29B Firmware","Huawei Paris-L21B","Huawei Sydney-L22 Firmware","Huawei Mate 20 X Firmware","Huawei Alp-L09 Firmware","Huawei Sydneym-L22","Huawei P30 Pro Firmware","Huawei Columbia-Al10B Firmware","Huawei Sydneym-Al00 Firmware","Huawei Nova Lite 3","Huawei Y9 2019 Firmware","Huawei Charlotte-L29C Firmware","Huawei Berkeley-Al20","Huawei Honor 10 Lite Firmware","Huawei Jackman-L22","Huawei Alp-Al00B Firmware","Huawei Ever-L29B","Huawei Cornell-Al00A","Huawei Mate 20 Pro Firmware","Huawei Mate 20 X","Huawei P30","Huawei Sydney-L22Br","Huawei Emily-L09C","Huawei Honor V20","Huawei Honor Magic2 Firmware","Huawei Jackman-L22 Firmware","Huawei Columbia-Al10B","Huawei Honor View 20 Firmware","Huawei Sydneym-L01","Huawei Columbia-L29D","Huawei Nova Lite 3 Firmware","Huawei Alp-L29 Firmware","Huawei Sydney-L22","Huawei Sydney-Al00 Firmware","Huawei Honor View 20","Huawei Sydneym-L21","Huawei Sydney-Al00","Huawei P20 Pro","Huawei Honor 20 Firmware","Huawei Alp-Al00B","Huawei Paris-L21Meb Firmware","Huawei Sydney-L21 Firmware","Huawei Mate 20 Rs Firmware","Huawei Sydney-L21Br Firmware","Huawei Emily-L09C Firmware","Huawei Sydneym-L21 Firmware","Huawei Sydneym-L03 Firmware","Huawei Columbia-L29D Firmware","Huawei Sydney-L21Br","Huawei Honor 8X","Huawei Honor Magic2","Huawei Sydneym-L23","Huawei P20","Huawei Mate 20 Pro","Huawei Sydney-L21","Huawei P20 Firmware","Huawei Bla-L29C Firmware","Huawei Paris-L21Meb","Huawei Paris-L29B","Huawei Yale-L21A","Huawei Honor 20","Huawei Y9 2019","Huawei Sydneym-L01 Firmware","Huawei Sydneym-L03","Huawei Berkeley-L09 Firmware","Huawei Honor V20 Firmware","Huawei Alp-L29","Huawei Charlotte-L09C Firmware","Huawei Mate 20 Firmware","Huawei Yale-L21A Firmware","Huawei Emily-L29C","Huawei Emily-L29C Firmware","Huawei Sydneym-L23 Firmware","Huawei Mate 20 Rs","Huawei Charlotte-L09C","Huawei Bla-L29C","Huawei Alp-L09","Huawei P20 Pro Firmware","Huawei Honor 8X Firmware","Huawei Sydneym-L22 Firmware","Huawei Berkeley-L09","Huawei P30 Firmware","Huawei Cornell-L29A","Huawei Charlotte-L29C","Huawei Cornell-Al00A Firmware",[245],"https:\u002F\u002Fwww.huawei.com\u002Fen\u002Fpsirt\u002Fsecurity-advisories\u002Fhuawei-sa-20190814-01-mobile-en",0.27,0.00323,0.25144,{"timestamp":6,"automatable":250,"tech_impact":251,"exploitation":252,"cisa_decision":253,"cisa_remediation_timeline":254},"no","partial","none",{},"FSU",[],[],{"count":258,"next":259,"previous":6,"results":260},26,"http:\u002F\u002Fweb:8606\u002Fapi\u002Farticles\u002F?page=2&page_size=3&sorted_by=-published_at",[261,269,277],{"id":262,"title":263,"summary":264,"published_at":265,"type":266,"link":267,"image_url":268},30,"PHP2Shell: Two Critical RCE Flaws in PHP (CVSS 9.2)","Unauthenticated code execution demonstrated on WordPress, Drupal and Joomla, and reproduced in our lab. Patched versions and steps to take today.","2026-10-22T00:00:00Z","cve","https:\u002F\u002Fpatrowl.io\u002Fen\u002Fblog\u002Fphp2shell-2-critical-rce-flaws-php-cvss-9-2","https:\u002F\u002Fpatrowl.io\u002Fmedia\u002Fsite\u002Fc0615c4ee6-1792684469\u002Fphp2shell-2-critical-rce-flaws-php-cvss-9-2.png",{"id":270,"title":271,"summary":272,"published_at":273,"type":274,"link":275,"image_url":276},29,"Manage External Security Across All Your Entities","Centralize the management of entities, users and external security resources while maintaining strict data isolation with Patrowl.","2026-09-15T00:00:00Z","security tips","https:\u002F\u002Fpatrowl.io\u002Fen\u002Fblog\u002Fmulti-entity-external-security-how-structure-governance-group-level","https:\u002F\u002Fpatrowl.io\u002Fmedia\u002Fsite\u002F8b2c0cc5eb-1789551467\u002Fvisu_1_multi_tenancy_dark_1x.webp",{"id":278,"title":279,"summary":280,"published_at":281,"type":282,"link":283,"image_url":284},28,"Will AI Become the Next Hacker? Bruce Schneier Answers at DEF CON 34","Tax law, finance, legislation: Bruce Schneier shows how AI could hack human rule systems just as easily as it hacks software.","2026-09-14T00:00:00Z","hacks","https:\u002F\u002Fpatrowl.io\u002Fen\u002Fblog\u002Fbruce-schneier-def-con-34","https:\u002F\u002Fpatrowl.io\u002Fmedia\u002Fsite\u002F5c616d9db4-1789462598\u002Fai-hacker.en.png"]