[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"landing-trending":3,"cve-CVE-2022-34411":30,"landing-articles":395},{"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":47,"cwes":48,"cpes":50,"technologies":211,"references":372,"score":374,"epss_score":375,"epss_percentile":376,"is_kev":47,"cisa_kev_date_added":6,"cisa_kev_due_date":6,"cisa_ssvc":377,"attack_mappings":387,"exploits":394},303999,"CVE-2022-34411","EUVD-2022-37366","\nDell PowerEdge BIOS and Dell Precision BIOS contain an Improper SMM communication buffer verification vulnerability. A local malicious user with high Privileges may potentially exploit this vulnerability to perform arbitrary code execution or cause denial of service.\n\n","2023-03-16T12:15:00Z",{"cvss_v3.1":37},{"scope":38,"version":39,"baseScore":40,"attackVector":41,"baseSeverity":42,"vectorString":43,"integrityImpact":44,"userInteraction":45,"attackComplexity":46,"availabilityImpact":44,"privilegesRequired":44,"confidentialityImpact":44},"UNCHANGED","3.1",6.7,"LOCAL","MEDIUM","CVSS:3.1\u002FAV:L\u002FAC:L\u002FPR:H\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H","HIGH","NONE","LOW",false,[49],"CWE-119",[51,52,53,54,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,149,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],"cpe:2.3:o:dell:r240_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:nx3240:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:c4130_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:t140_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:r940:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r430:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r540:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:c6320:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r750xa_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:xr11:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:t150_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:xe7440_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:fc830_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:m630_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:nx3230_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:xr12:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:m830p_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:c6320_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:c6525:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:xe8545_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:r930:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r650xs:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r730xd:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:fc430_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:nx3230:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r7425_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:mx740c_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:m630p_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:t550:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:m630:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r630_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:r7525:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:t630:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:fc630_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:r330_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:r6515_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:t440:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:nx3330_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:m640p_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:r250:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:xe7440:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:xe8545:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:c4140_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:r840_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:r750:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:dss8440:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:xr2_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:fc830:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:nx3340:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:c6520_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:r540_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:r550:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:t640:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:c6520:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:fc640:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:m640:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:m630p:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r230:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r750_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:t550_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:r350:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r930_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:r240:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r6525:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r740xd2_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:r840:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r7415_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:t330:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r940xa_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:c6420:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r940xa:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r340:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:t630_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:t350:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:m640_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:r730xd_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:r6515:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:t350_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:xr12_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:c4140:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:nx3330:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r740_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:xr2:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r7415:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:t430_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:r550_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:t340:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r530:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:nx430:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r640:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:mx840c:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:t430:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:m830_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:r7525_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:xe7420:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:mx750c:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:nx3340_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:m640p:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:m830p:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r230_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:r740:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r750xs:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r7425:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:t150:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:mx740c:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r740xd2:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r450:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r430_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:c4130:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:xr11_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:dss8440_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:r640_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:c6525_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:fc430:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:t340_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:r630:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r530_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:r750xs_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:nx3240_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:t130_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:r440:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r450_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:r6525_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:r750xa:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:mx840c_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:mx750c_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:t640_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:nx440:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r7515:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:fc640_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:r340_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:r830:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r650xs_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:t140:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r440_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:c6420_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:t330_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:r730:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r830_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:m830:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r6415:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r740xd_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:nx440_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:r650_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:r250_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:t440_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:r730_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:nx430_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:t130:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r330:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r350_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:xe2420_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:r6415_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:dell:xe7420_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:r650:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r940_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:dell:fc630:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:r740xd:-:*:*:*:*:*:*:*","cpe:2.3:h:dell:xe2420:-:*:*:*:*:*:*:*","cpe:2.3:o:dell:r7515_firmware:*:*:*:*:*:*:*:*",[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,244,245,246,247,248,249,250,251,252,253,254,255,256,257,258,259,260,261,262,263,264,265,266,267,268,269,270,271,272,273,274,275,276,277,278,279,280,281,282,283,284,285,286,287,288,289,290,291,292,293,294,295,296,297,298,299,300,301,302,303,304,305,306,307,308,309,310,311,312,313,314,315,316,317,318,319,320,321,322,323,324,325,326,327,328,329,330,331,332,333,334,335,336,337,338,339,340,341,342,343,344,345,346,347,348,349,350,351,352,353,354,355,356,357,358,359,360,361,362,363,364,365,366,367,368,369,370,371],"Dell R7525","Dell C6320","Dell C6525 Firmware","Dell C4140","Dell T150","Dell R740 Firmware","Dell R750Xa Firmware","Dell R6525","Dell R630","Dell T440","Dell Nx3240","Dell T130","Dell T350 Firmware","Dell T440 Firmware","Dell R750","Dell R940Xa Firmware","Dell R450 Firmware","Dell T640","Dell Xe7440","Dell Nx440","Dell R740Xd2 Firmware","Dell R450","Dell R930","Dell M830P","Dell Xe7440 Firmware","Dell M640P Firmware","Dell M640","Dell R7425","Dell T340","Dell R740","Dell Dss8440","Dell T140","Dell C6320 Firmware","Dell Fc830 Firmware","Dell R6515","Dell R350 Firmware","Dell T430","Dell R540","Dell R240","Dell Fc640 Firmware","Dell C4140 Firmware","Dell M630","Dell T550","Dell Xr12","Dell R440","Dell R740Xd Firmware","Dell R250 Firmware","Dell Fc630 Firmware","Dell C6420 Firmware","Dell Xr11 Firmware","Dell Mx840C","Dell R6415 Firmware","Dell R550 Firmware","Dell Fc430","Dell R6525 Firmware","Dell Xr2","Dell C4130 Firmware","Dell Xr2 Firmware","Dell T630 Firmware","Dell R230","Dell R7525 Firmware","Dell Xe7420","Dell R240 Firmware","Dell Mx740C","Dell R7515 Firmware","Dell Fc430 Firmware","Dell T630","Dell R740Xd2","Dell Fc630","Dell T340 Firmware","Dell T430 Firmware","Dell R830","Dell R940 Firmware","Dell Nx430","Dell R330 Firmware","Dell Nx3340 Firmware","Dell C6420","Dell Xe2420","Dell Nx430 Firmware","Dell T130 Firmware","Dell M830P Firmware","Dell R7425 Firmware","Dell T330","Dell R530 Firmware","Dell R650Xs","Dell R540 Firmware","Dell M630P","Dell R930 Firmware","Dell R750 Firmware","Dell R750Xa","Dell Mx750C","Dell R640","Dell Xe2420 Firmware","Dell T550 Firmware","Dell Xr11","Dell R650Xs Firmware","Dell R730 Firmware","Dell R6415","Dell R330","Dell R440 Firmware","Dell T350","Dell C6520 Firmware","Dell Mx750C Firmware","Dell Mx740C Firmware","Dell T140 Firmware","Dell R340","Dell R630 Firmware","Dell Nx3240 Firmware","Dell M640 Firmware","Dell Nx3330","Dell T330 Firmware","Dell R740Xd","Dell Nx3230 Firmware","Dell T150 Firmware","Dell R550","Dell M830","Dell R840","Dell M630 Firmware","Dell R7515","Dell Xe8545 Firmware","Dell R650","Dell Fc830","Dell R7415 Firmware","Dell R940Xa","Dell R650 Firmware","Dell R350","Dell Fc640","Dell Xe8545","Dell R750Xs","Dell T640 Firmware","Dell Nx440 Firmware","Dell Nx3230","Dell R730Xd","Dell R7415","Dell R250","Dell C6520","Dell Nx3340","Dell Xe7420 Firmware","Dell R830 Firmware","Dell R840 Firmware","Dell R340 Firmware","Dell R430","Dell R750Xs Firmware","Dell Xr12 Firmware","Dell R430 Firmware","Dell R230 Firmware","Dell C4130","Dell R730","Dell M640P","Dell R530","Dell R640 Firmware","Dell Nx3330 Firmware","Dell Mx840C Firmware","Dell Dss8440 Firmware","Dell R730Xd Firmware","Dell M830 Firmware","Dell R6515 Firmware","Dell R940","Dell C6525","Dell M630P Firmware",[373],"https:\u002F\u002Fwww.dell.com\u002Fsupport\u002Fkbdoc\u002Fen-us\u002F000206296\u002Fdsa-2022-204-dell-poweredge-improper-smm-communication-buffer-verification-vulnerability",0.34,0.00172,0.06587,{"timestamp":378,"automatable":379,"tech_impact":380,"exploitation":381,"cisa_decision":382,"cisa_remediation_timeline":386},"2025-02-26T16:03:59.875459Z","no","total","none",{"vector":383,"decision":384,"priority":385},"CISAv1\u002FE:N\u002FA:N\u002FT:T\u002FM:H\u002F2026-10-26T03:07:19.643466\u002F","track_star","medium","14D",[388],{"name":389,"source":390,"tactics":391,"technique_id":393},"Exploitation for Privilege Escalation","attack_vector",[392],"privilege-escalation","T1068",[],{"count":396,"next":397,"previous":6,"results":398},26,"http:\u002F\u002Fweb:8606\u002Fapi\u002Farticles\u002F?page=2&page_size=3&sorted_by=-published_at",[399,407,415],{"id":400,"title":401,"summary":402,"published_at":403,"type":404,"link":405,"image_url":406},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":408,"title":409,"summary":410,"published_at":411,"type":412,"link":413,"image_url":414},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":416,"title":417,"summary":418,"published_at":419,"type":420,"link":421,"image_url":422},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"]