[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"landing-trending":3,"cve-CVE-2024-22194":30,"landing-articles":111},{"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":51,"technologies":65,"references":70,"score":89,"epss_score":90,"epss_percentile":91,"is_kev":47,"cisa_kev_date_added":6,"cisa_kev_due_date":6,"cisa_ssvc":92,"attack_mappings":102,"exploits":109},54194,"CVE-2024-22194","EUVD-2024-0020","cdo-local-uuid vulnerable to insertion of artifact derived from developer's Present Working Directory into demonstration code\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nAn information leakage vulnerability is present in [`cdo-local-uuid`](https:\u002F\u002Fpypi.org\u002Fproject\u002Fcdo-local-uuid\u002F) at version `0.4.0`, and in [`case-utils`](https:\u002F\u002Fpypi.org\u002Fproject\u002Fcase-utils\u002F) in unpatched versions (matching the pattern `0.x.0`) at and since `0.5.0`, before `0.15.0`.\n\nThe vulnerability stems from a Python function, `cdo_local_uuid.local_uuid()`, and its original implementation `case_utils.local_uuid()`.  Henceforth, both will be called `local_uuid()`.\n\n`local_uuid()` generates UUIDv5s using a deterministic pseudorandom number stream.  This was written to make graph application demonstrations generate consistent, version-controllable output with minimal noise caused by demonstration re-runs.  Part of the information used to keep individual examples' generated output distinct from one another is seed information from the caller's environment, particularly the program's argument vector.  The present working directory is also included as part of the seed information, but for reasons including maintaining user environment privacy, as well as keeping generated identifiers consistent regardless of where a source tree is housed on a user's file system, the present working directory is trimmed from the left to exclude path information outside of a supplied \"Top\" source directory.  (In context of the Make scripting language, this \"top\" directory is typically in a variable called `top_srcdir`.  In context of Git-based project management, this directory is expected to be the root directory of a freshly \"Cloned\" project, e.g., where `.git` is stored.)\n\nUnder certain conditions, a user's present working directory, as an absolute path, was incorporated into seed data for the `local_uuid()` deterministic pseudorandom number stream.  This violates an expectation made in the documented purpose of the `local_uuid()` function, and leaks information about a calling user's environment.\n\nThe conditions are:\n\n* Given a project with top source directory `top_srcdir`, for instance `\u002Fhome\u002Fuser1\u002FDocuments\u002FProject1`;\n* Given a Python script housed directly in `top_srcdir`, for instance at `${top_srcdir}\u002Fexample.py`, written to support the deterministic mode of `local_uuid()`;\n* Given a call to that Python script that follows the documentation for `local_uuid()`;\n\nThe absolute path for `top_srcdir` was then included in the seed information for the UUIDv5 stream, when what was intended was a relative path spelling.  That is, instead of `.\u002Fexample.py` being in the seed data, `\u002Fhome\u002Fuser1\u002FDocuments\u002FProject1\u002Fexample.py` was in the seed data.\n\nThis does not leak the present working directory directly.  But, given other knowledge of how a program had been called to generate data using `local_uuid()` under these conditions, it becomes possible to determine that a chosen path can lead to a known UUIDv5 value.  Note that it is not necessarily knowable that the chosen path is the *only* solution to a sequence reconstruction; but, the path can be confirmed to be *a* solution.\n\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nThe issue has been patched, in the `cdo-local-uuid` source repository and the `case-utils` source repository.\n\nUsers should upgrade to any of these versions minimally:\n\n* `case-utils == 0.5.1`\n* `case-utils == 0.6.1`\n* `case-utils == 0.7.1`\n* `case-utils == 0.8.1`\n* `case-utils == 0.9.1`\n* `case-utils == 0.10.1`\n* `case-utils == 0.11.1`\n* `case-utils == 0.12.1`\n* `case-utils == 0.13.1`\n* `case-utils == 0.14.1`\n* `case-utils >= 0.15.0`\n* `cdo-local-uuid == 0.5.0`\n\nAll `case-utils` releases that contain the patch have the commit `ea630cce66b26dae6d7fa7e02451d6e25456a5f2` in their Git history.  Anyone interested in confirming the presence of this commit in a certain branch or tag can run the following test (written in Bash), substituting the desired branch name for the assigned value of `my_git_ref_of_interest`:\n\n```bash\n#!\u002Fbin\u002Fbash\n# Present working directory ($PWD) should be in a clone of this repository:\n# https:\u002F\u002Fgithub.com\u002Fcasework\u002FCASE-Utilities-Python\nmy_git_ref_of_interest=main\ntest \\\n  \"xea630cce66b26dae6d7fa7e02451d6e25456a5f2\" \\\n  == \\\n  \"x$(git merge-base ea630cc ${my_git_ref_of_interest})\"\necho $?  # Should print '0'\n```\n\nNote that other releases have been posted atop some of those minimal versions recommended for upgrading, named, e.g., `0.5.1.post0`.  These releases were posted to update internal library version numbers, and otherwise contain no functional changes, in accordance with Python Packaging guidance:\n\n* https:\u002F\u002Fpackaging.python.org\u002Fen\u002Flatest\u002Fspecifications\u002Fversion-specifiers\u002F#post-release-separators\n\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nIf the script calling `cdo_local_uuid.local_uuid()` is moved out of the \"Top\" source directory, the issue is addressed.\n\n\n### References\n_Are there any links users can visit to find out more?_\n\nThe issue is addressed in this Pull Request:\n\n* https:\u002F\u002Fgithub.com\u002FCyber-Domain-Ontology\u002FCDO-Utility-Local-UUID\u002Fpull\u002F3\n\nTests to reproduce the issue's conditions and confirm it has been addressed are in this Pull Requested:\n\n* https:\u002F\u002Fgithub.com\u002FCyber-Domain-Ontology\u002FCDO-Utility-Local-UUID\u002Fpull\u002F4\n\n\u003C!--\nCVSS3.1 vector determined by rubric diagrams at this page:\nhttps:\u002F\u002Fwww.first.org\u002Fcvss\u002Fv3.1\u002Fuser-guide\n-->","2024-01-11T15:18: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":42,"confidentialityImpact":42},"UNCHANGED","3.1",2.2,"LOCAL","LOW","CVSS:3.1\u002FAV:L\u002FAC:H\u002FPR:L\u002FUI:R\u002FS:U\u002FC:L\u002FI:N\u002FA:N","NONE","REQUIRED","HIGH",false,[49,50],"CWE-337","CWE-215",[52,53,54,55,56,57,58,59,60,61,62,63,64],"cpe:2.3:a:lfprojects:case_python_utilities:0.6.0:*:*:*:*:python:*:*","cpe:2.3:a:lfprojects:case_python_utilities:0.8.0:*:*:*:*:python:*:*","cpe:2.3:a:lfprojects:case_python_utilities:0.11.0:*:*:*:*:python:*:*","cpe:2.3:a:lfprojects:case_python_utilities:0.13.0:*:*:*:*:python:*:*","cpe:2.3:a:lfprojects:cdo_local_uuid_utility:0.4.0:*:*:*:*:python:*:*","cpe:2.3:a:lfprojects:case_python_utilities:0.14.0:*:*:*:*:python:*:*","cpe:2.3:a:lfprojects:case_python_utilities:0.7.0:*:*:*:*:python:*:*","cpe:2.3:a:lfprojects:case_python_utilities:0.5.0:*:*:*:*:python:*:*","cpe:2.3:a:lfprojects:case_python_utilities:0.9.0:*:*:*:*:python:*:*","cpe:2.3:a:lfprojects:case_python_utilities:0.10.0:*:*:*:*:python:*:*","cpe:2.3:a:lfprojects:case_python_utilities:0.12.0:*:*:*:*:python:*:*","cpe:2.3:a:cdo-local-uuid:cdo-local-uuid:*:*:*:*:*:*:*:*","cpe:2.3:a:case-utils:case-utils:*:*:*:*:*:*:*:*",[66,67,68,69],"Lfprojects Case Python Utilities","Lfprojects Cdo Local Uuid Utility","Cdo-Local-Uuid Cdo-Local-Uuid","Case-Utils Case-Utils",[71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88],"https:\u002F\u002Fgithub.com\u002FCyber-Domain-Ontology\u002FCDO-Utility-Local-UUID\u002Fcommit\u002F9e78f7cb1075728d0aafc918514f32a1392cd235","https:\u002F\u002Fgithub.com\u002FCyber-Domain-Ontology\u002FCDO-Utility-Local-UUID\u002Fpull\u002F3","https:\u002F\u002Fgithub.com\u002FCyber-Domain-Ontology\u002FCDO-Utility-Local-UUID\u002Fpull\u002F4","https:\u002F\u002Fgithub.com\u002FCyber-Domain-Ontology\u002FCDO-Utility-Local-UUID\u002Fsecurity\u002Fadvisories\u002FGHSA-rgrf-6mf5-m882","https:\u002F\u002Fgithub.com\u002Fcasework\u002FCASE-Utilities-Python\u002Fcommit\u002F00864cd12de7c50d882dd1a74915d32e939c25f9","https:\u002F\u002Fgithub.com\u002Fcasework\u002FCASE-Utilities-Python\u002Fcommit\u002F1cccae8eb3cf94b3a28f6490efa0fbf5c82ebd6b","https:\u002F\u002Fgithub.com\u002Fcasework\u002FCASE-Utilities-Python\u002Fcommit\u002F5acb929dfb599709d1c8c90d1824dd79e0fd9e10","https:\u002F\u002Fgithub.com\u002Fcasework\u002FCASE-Utilities-Python\u002Fcommit\u002F7e02d18383eabbeb9fb4ec97d81438c9980a4790","https:\u002F\u002Fgithub.com\u002Fcasework\u002FCASE-Utilities-Python\u002Fcommit\u002F80551f49241c874c7c50e14abe05c5017630dad2","https:\u002F\u002Fgithub.com\u002Fcasework\u002FCASE-Utilities-Python\u002Fcommit\u002F939775f956796d0432ecabbf62782ed7ad1007b5","https:\u002F\u002Fgithub.com\u002Fcasework\u002FCASE-Utilities-Python\u002Fcommit\u002Fdb428a0745dac4fdd888ced9c52f617695519f9d","https:\u002F\u002Fgithub.com\u002Fcasework\u002FCASE-Utilities-Python\u002Fcommit\u002Fe4ffadc3d56fd303b8f465d727c4a58213d311a1","https:\u002F\u002Fgithub.com\u002Fcasework\u002FCASE-Utilities-Python\u002Fcommit\u002Ffca7388f09feccd3b9ea88e6df9c7a43a5349452","https:\u002F\u002Fgithub.com\u002Fcasework\u002FCASE-Utilities-Python\u002Fcommit\u002Ffdc32414eccfcbde6be0fd91b7f491cc0779b02d#diff-e60b9cb8fb480ed27283a030a0898be3475992d78228f4045b12ce5cbb2f0509","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2024-22194","https:\u002F\u002Fgithub.com\u002Fpypa\u002Fadvisory-database\u002Ftree\u002Fmain\u002Fvulns\u002Fcase-utils\u002FPYSEC-2024-5.yaml","https:\u002F\u002Fgithub.com\u002Fpypa\u002Fadvisory-database\u002Ftree\u002Fmain\u002Fvulns\u002Fcdo-local-uuid\u002FPYSEC-2024-6.yaml","https:\u002F\u002Fgithub.com\u002FCyber-Domain-Ontology\u002FCDO-Utility-Local-UUID",0.26,0.0041,0.3494,{"timestamp":93,"automatable":94,"tech_impact":95,"exploitation":96,"cisa_decision":97,"cisa_remediation_timeline":101},"2025-05-08T20:11:54.538835Z","no","partial","poc",{"vector":98,"decision":99,"priority":100},"CISAv1\u002FE:P\u002FA:N\u002FT:P\u002FM:H\u002F2026-10-26T06:08:01.281927\u002F","track_star","medium","60D",[103],{"name":104,"source":105,"tactics":106,"technique_id":108},"Exploitation for Privilege Escalation","attack_vector",[107],"privilege-escalation","T1068",[110],{"link":74},{"count":112,"next":113,"previous":6,"results":114},26,"http:\u002F\u002Fweb:8606\u002Fapi\u002Farticles\u002F?page=2&page_size=3&sorted_by=-published_at",[115,123,131],{"id":116,"title":117,"summary":118,"published_at":119,"type":120,"link":121,"image_url":122},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":124,"title":125,"summary":126,"published_at":127,"type":128,"link":129,"image_url":130},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":132,"title":133,"summary":134,"published_at":135,"type":136,"link":137,"image_url":138},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"]