[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"landing-trending":3,"cve-CVE-2026-72419":30,"landing-articles":78},{"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":46,"cwes":47,"cpes":48,"technologies":49,"references":50,"score":57,"epss_score":58,"epss_percentile":59,"is_kev":46,"cisa_kev_date_added":6,"cisa_kev_due_date":6,"cisa_ssvc":60,"attack_mappings":70,"exploits":77},376741,"CVE-2026-72419","EUVD-2026-59318","In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_nat: avoid invalid nat_net pointer use on failed nf_nat_init()\n\nWe ran into below KASAN splat, which is mostly uninteresting, beside\nfor having nf_nat_register_fn() in the call chain as a cause for the\noffending access:\n\n==================================================================\nBUG: KASAN: slab-out-of-bounds in nf_nat_register_fn+0x5f9\u002F0x640\nRead of size 8 at addr ffff890031e54c20 by task iptables\u002F9510\n\nCPU: 0 UID: 0 PID: 9510 Comm: iptables Not tainted 6.18.18-grsec-full-20260320181326 #1 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04\u002F01\u002F2014\nCall Trace:\n \u003CTASK>\n […] dump_stack_lvl+0xee\u002F0x160 ffff88004117eeb8\n […] print_report+0x6e\u002F0x640 ffff88004117eee0\n […] ? __phys_addr+0x8e\u002F0x140 ffff88004117eef0\n […] ? kasan_addr_to_slab+0x51\u002F0xe0 ffff88004117ef08\n […] ? complete_report_info+0xec\u002F0x1c0 ffff88004117ef20\n […] ? nf_nat_register_fn+0x5f9\u002F0x640 ffff88004117ef48\n […] kasan_report+0xbc\u002F0x140 ffff88004117ef50\n […] ? nf_nat_register_fn+0x5f9\u002F0x640 ffff88004117ef90\n […] nf_nat_register_fn+0x5f9\u002F0x640 ffff88004117eff8\n […] ? nf_nat_icmp_reply_translation+0x6e0\u002F0x6e0 ffff88004117f070\n […] nf_tables_register_hook.part.0+0xa0\u002F0x220 ffff88004117f080\n […] nf_tables_addchain.constprop.0+0x1054\u002F0x1fc0 ffff88004117f0b8\n […] ? nft_chain_lookup.part.0+0x4ce\u002F0xac0 ffff88004117f130\n […] ? nf_tables_abort+0x3d80\u002F0x3d80 ffff88004117f190\n […] ? nf_tables_dumpreset_obj+0x100\u002F0x100 ffff88004117f1c8\n […] ? nft_table_lookup.part.0+0x255\u002F0x300 ffff88004117f310\n […] ? nf_tables_newchain+0x21a4\u002F0x2fa0 ffff88004117f358\n […] nf_tables_newchain+0x21a4\u002F0x2fa0 ffff88004117f360\n […] ? nf_tables_addchain.constprop.0+0x1fc0\u002F0x1fc0 ffff88004117f458\n […] ? nla_get_range_signed+0x4a0\u002F0x4a0 ffff88004117f488\n […] ? lock_acquire+0x16f\u002F0x320 ffff88004117f490\n […] ? find_held_lock+0x3b\u002F0xe0 ffff88004117f4b0\n […] ? __nla_parse+0x45\u002F0x80 ffff88004117f500\n […] nfnetlink_rcv_batch+0xbca\u002F0x19a0 ffff88004117f550\n […] ? nfnetlink_net_exit_batch+0x120\u002F0x120 ffff88004117f618\n […] ? __sanitizer_cov_trace_switch+0x63\u002F0xe0 ffff88004117f720\n […] ? gr_acl_handle_mmap+0x1c4\u002F0x320 ffff88004117f7c0\n […] ? nla_get_range_signed+0x4a0\u002F0x4a0 ffff88004117f7e8\n […] ? gr_is_capable+0x6f\u002F0xe0 ffff88004117f830\n […] ? __nla_parse+0x45\u002F0x80 ffff88004117f860\n […] ? skb_pull+0x103\u002F0x1a0 ffff88004117f880\n […] nfnetlink_rcv+0x3db\u002F0x4a0 ffff88004117f8b0\n […] ? nfnetlink_rcv_batch+0x19a0\u002F0x19a0 ffff88004117f8d8\n […] ? netlink_lookup+0xe2\u002F0x240 ffff88004117f900\n […] netlink_unicast+0x74b\u002F0xb00 ffff88004117f930\n […] ? netlink_attachskb+0xb20\u002F0xb20 ffff88004117f980\n […] ? __check_object_size+0x3e\u002F0xaa0 ffff88004117f998\n […] ? security_netlink_send+0x51\u002F0x160 ffff88004117f9c8\n […] netlink_sendmsg+0xa03\u002F0x1200 ffff88004117f9f8\n […] ? netlink_unicast+0xb00\u002F0xb00 ffff88004117fa70\n […] ? netlink_unicast+0xb00\u002F0xb00 ffff88004117fac8\n […] ? ____sys_sendmsg+0xe2a\u002F0x1040 ffff88004117faf8\n […] ____sys_sendmsg+0xe2a\u002F0x1040 ffff88004117fb00\n […] ? kernel_recvmsg+0x300\u002F0x300 ffff88004117fb60\n […] ? reacquire_held_locks+0xe9\u002F0x260 ffff88004117fbc8\n […] ___sys_sendmsg+0x138\u002F0x200 ffff88004117fbf8\n […] ? do_recvmmsg+0x7e0\u002F0x7e0 ffff88004117fc30\n […] ? lockdep_hardirqs_on_prepare+0x101\u002F0x1e0 ffff88004117fc50\n […] ? lock_acquire+0x16f\u002F0x320 ffff88004117fd20\n […] ? lock_acquire+0x16f\u002F0x320 ffff88004117fd58\n […] ? find_held_lock+0x3b\u002F0xe0 ffff88004117fd70\n […] __sys_sendmsg+0x17a\u002F0x260 ffff88004117fdc8\n […] ? __sys_sendmsg_sock+0x80\u002F0x80 ffff88004117fdf0\n […] ? syscall_trace_enter+0x15e\u002F0x2c0 ffff88004117fe98\n […] do_syscall_64+0x7d\u002F0x400 ffff88004117fec8\n […] entry_SYSCALL_64_safe_stack+0x4a\u002F0x60 ffff88004117fef8\n \u003C\u002FTASK>\n==================================================================\n\nThe out-of-bounds report, though, is a red herring as it is f\n---truncated---","2026-08-15T06:22:00Z",{"cvss_v3.1":37},{"scope":38,"version":39,"baseScore":40,"attackVector":41,"baseSeverity":42,"vectorString":43,"integrityImpact":42,"userInteraction":44,"attackComplexity":45,"availabilityImpact":42,"privilegesRequired":45,"confidentialityImpact":42},"UNCHANGED","3.1",7.8,"LOCAL","HIGH","CVSS:3.1\u002FAV:L\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H","NONE","LOW",false,[],[],[],[51,52,53,54,55,56],"https:\u002F\u002Fgit.kernel.org\u002Fstable\u002Fc\u002F069cfe3de2a5e16069485893cd04665ab769c1d8","https:\u002F\u002Fgit.kernel.org\u002Fstable\u002Fc\u002F359d8ff97362a4662356104540e4814bff9dad7c","https:\u002F\u002Fgit.kernel.org\u002Fstable\u002Fc\u002F87f7a720de2545fdac29c85acb7163676feacdaf","https:\u002F\u002Fgit.kernel.org\u002Fstable\u002Fc\u002Fa73e7ac3f3b69e9581ec7bfd889ff3e9b8c773f7","https:\u002F\u002Fgit.kernel.org\u002Fstable\u002Fc\u002Fe794f633021defcfa98e17d73b955cd07590831f","https:\u002F\u002Fgit.kernel.org\u002Fstable\u002Fc\u002Feb14aba91163c33d8c99f9d7c06690e08b56a250",0.39,0.00176,0.07051,{"timestamp":61,"automatable":62,"tech_impact":63,"exploitation":64,"cisa_decision":65,"cisa_remediation_timeline":69},"2026-10-16T18:49:26.468159Z","no","total","none",{"vector":66,"decision":67,"priority":68},"CISAv1\u002FE:N\u002FA:N\u002FT:T\u002FM:H\u002F2026-10-26T06:04:20.187353\u002F","track_star","medium","14D",[71],{"name":72,"source":73,"tactics":74,"technique_id":76},"Exploitation for Privilege Escalation","attack_vector",[75],"privilege-escalation","T1068",[],{"count":79,"next":80,"previous":6,"results":81},26,"http:\u002F\u002Fweb:8606\u002Fapi\u002Farticles\u002F?page=2&page_size=3&sorted_by=-published_at",[82,90,98],{"id":83,"title":84,"summary":85,"published_at":86,"type":87,"link":88,"image_url":89},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":91,"title":92,"summary":93,"published_at":94,"type":95,"link":96,"image_url":97},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":99,"title":100,"summary":101,"published_at":102,"type":103,"link":104,"image_url":105},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"]