[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"landing-trending":3,"cve-CVE-2017-9852":30,"landing-articles":254},{"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":52,"cwes":53,"cpes":55,"technologies":134,"references":213,"score":217,"epss_score":218,"epss_percentile":219,"is_kev":220,"cisa_kev_date_added":6,"cisa_kev_due_date":6,"cisa_ssvc":221,"attack_mappings":227,"exploits":253},206031,"CVE-2017-9852","EUVD-2017-18762","An Incorrect Password Management issue was discovered in SMA Solar Technology products. Default passwords exist that are rarely changed. User passwords will almost always be default. Installer passwords are expected to be default or similar across installations installed by the same company (but are sometimes changed). Hidden user accounts have (at least in some cases, though more research is required to test this for all hidden user accounts) a fixed password for all devices; it can never be changed by a user. Other vulnerabilities exist that allow an attacker to get the passwords of these hidden user accounts. NOTE: the vendor reports that it has no influence on the allocation of passwords, and that global hardcoded master passwords do not exist. Also, only Sunny Boy TLST-21 and TL-21 and Sunny Tripower TL-10 and TL-30 could potentially be affected","2017-08-05T17:29:00Z",{"cvss_v2.0":37,"cvss_v3.0":45},{"version":38,"baseScore":39,"accessVector":40,"vectorString":41,"authentication":42,"integrityImpact":42,"accessComplexity":43,"availabilityImpact":42,"confidentialityImpact":44},"2.0",5,"NETWORK","AV:N\u002FAC:L\u002FAu:N\u002FC:P\u002FI:N\u002FA:N","NONE","LOW","PARTIAL",{"scope":46,"version":47,"baseScore":48,"attackVector":40,"baseSeverity":49,"vectorString":50,"integrityImpact":51,"userInteraction":42,"attackComplexity":43,"availabilityImpact":51,"privilegesRequired":42,"confidentialityImpact":51},"UNCHANGED","3.0",9.8,"CRITICAL","CVSS:3.0\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H","HIGH",true,[54],"CWE-798",[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],"cpe:2.3:h:sma:sunny_boy_3000tl:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_storage_630_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_storage_800:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_boy_2.5:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_storage_2200:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_tripower_core1:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_storage_720_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_storage_1000:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_tripower_15000tl_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_boy_3600tl:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_720cp_xt_firmware:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_storage_500_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_storage_2500-ev:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_tripower_60:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_tripower_5000tl:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_storage_800_firmware:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_800cp_xt_firmware:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_760cp_xt_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_720cp_xt:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_boy_storage_2.5:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_storage_760_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_storage_760:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_storage_500:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_boy_3.6_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_500cp_xt:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_boy_2.5_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_boy_3600:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_storage_2500-ev_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_boy_3.6:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_boy_3600tl_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_2200:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_boy_storage_2.5_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_tripower_12000tl:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_tripower_15000tl:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_850cp_xt_firmware:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_630cp_xt_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_850cp_xt:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_boy_3600_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_boy_5000tl:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_tripower_20000tl_firmware:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_boy_5000tl_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_tripower_20000tl:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_tripower_5000tl_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_boy_1.5:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_boy_5000:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_1000cp_xt_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_760cp_xt:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_tripower_25000tl_firmware:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_boy_4000tl_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_boy_4000tl:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_storage_850_firmware:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_boy_4.0_firmware:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_tripower_core1_firmware:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_boy_3000tl_firmware:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_900cp_xt_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_boy_5.0:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_storage_850:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_boy_4.0:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_900cp_xt:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_tripower_12000tl_firmware:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_storage_900_firmware:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_boy_3.0_firmware:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_2200_firmware:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_boy_5.0_firmware:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_storage_1000_firmware:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_boy_1.5_firmware:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_tripower_60_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_1000cp_xt:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_storage_900:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_tripower_25000tl:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_storage_2200_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_storage_720:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_central_500cp_xt_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_storage_630:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_630cp_xt:-:*:*:*:*:*:*:*","cpe:2.3:o:sma:sunny_boy_5000_firmware:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_central_800cp_xt:-:*:*:*:*:*:*:*","cpe:2.3:h:sma:sunny_boy_3.0:-:*:*:*:*:*:*:*",[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],"Sma Sunny Central Storage 900 Firmware","Sma Sunny Central Storage 760","Sma Sunny Boy 3000Tl Firmware","Sma Sunny Central Storage 630","Sma Sunny Central 720Cp Xt","Sma Sunny Central 900Cp Xt","Sma Sunny Boy Storage 2.5","Sma Sunny Boy 5.0","Sma Sunny Boy 2.5","Sma Sunny Central Storage 850","Sma Sunny Central 720Cp Xt Firmware","Sma Sunny Boy 3.6 Firmware","Sma Sunny Central 1000Cp Xt","Sma Sunny Tripower Core1","Sma Sunny Central 2200","Sma Sunny Central 800Cp Xt Firmware","Sma Sunny Boy 3600Tl","Sma Sunny Boy 4.0 Firmware","Sma Sunny Central Storage 1000 Firmware","Sma Sunny Boy Storage 2.5 Firmware","Sma Sunny Central Storage 630 Firmware","Sma Sunny Central Storage 500 Firmware","Sma Sunny Tripower 60 Firmware","Sma Sunny Boy 3600","Sma Sunny Central 850Cp Xt","Sma Sunny Boy 1.5 Firmware","Sma Sunny Central 1000Cp Xt Firmware","Sma Sunny Boy 5000Tl Firmware","Sma Sunny Central Storage 500","Sma Sunny Central 800Cp Xt","Sma Sunny Boy 5000 Firmware","Sma Sunny Central 500Cp Xt Firmware","Sma Sunny Central Storage 720","Sma Sunny Central Storage 1000","Sma Sunny Boy 5.0 Firmware","Sma Sunny Central 760Cp Xt Firmware","Sma Sunny Tripower 15000Tl Firmware","Sma Sunny Central 900Cp Xt Firmware","Sma Sunny Boy 2.5 Firmware","Sma Sunny Boy 4000Tl Firmware","Sma Sunny Boy 3.0","Sma Sunny Tripower Core1 Firmware","Sma Sunny Boy 3600 Firmware","Sma Sunny Tripower 12000Tl","Sma Sunny Boy 3600Tl Firmware","Sma Sunny Tripower 20000Tl","Sma Sunny Boy 5000","Sma Sunny Tripower 12000Tl Firmware","Sma Sunny Tripower 5000Tl","Sma Sunny Tripower 15000Tl","Sma Sunny Central 500Cp Xt","Sma Sunny Central 2200 Firmware","Sma Sunny Central Storage 800","Sma Sunny Tripower 20000Tl Firmware","Sma Sunny Tripower 25000Tl","Sma Sunny Central Storage 850 Firmware","Sma Sunny Central Storage 2200 Firmware","Sma Sunny Boy 3.6","Sma Sunny Central Storage 720 Firmware","Sma Sunny Tripower 5000Tl Firmware","Sma Sunny Central Storage 800 Firmware","Sma Sunny Boy 3.0 Firmware","Sma Sunny Central Storage 2200","Sma Sunny Tripower 60","Sma Sunny Tripower 25000Tl Firmware","Sma Sunny Central Storage 2500-Ev","Sma Sunny Boy 4.0","Sma Sunny Central 630Cp Xt Firmware","Sma Sunny Central 760Cp Xt","Sma Sunny Central Storage 900","Sma Sunny Boy 3000Tl","Sma Sunny Central 630Cp Xt","Sma Sunny Boy 5000Tl","Sma Sunny Central 850Cp Xt Firmware","Sma Sunny Central Storage 2500-Ev Firmware","Sma Sunny Central Storage 760 Firmware","Sma Sunny Boy 1.5","Sma Sunny Boy 4000Tl",[214,215,216],"http:\u002F\u002Fwww.sma.de\u002Fen\u002Fstatement-on-cyber-security.html","http:\u002F\u002Fwww.sma.de\u002Ffileadmin\u002Fcontent\u002Fglobal\u002Fspecials\u002Fdocuments\u002Fcyber-security\u002FWhitepaper-Cyber-Security-AEN1732_07.pdf","https:\u002F\u002Fhorusscenario.com\u002FCVE-information\u002F",0.69,0.01716,0.77247,false,{"timestamp":6,"automatable":222,"tech_impact":223,"exploitation":224,"cisa_decision":225,"cisa_remediation_timeline":226},"no","partial","none",{},"FSU",[228,234,245],{"name":229,"source":230,"tactics":231,"technique_id":233},"Exploit Public-Facing Application","attack_vector",[232],"initial-access","T1190",{"name":235,"source":236,"cwe_ids":237,"tactics":238,"capec_ids":242,"technique_id":244},"Default Accounts","capec",[54],[232,239,240,241],"persistence","privilege-escalation","stealth",[243],"CAPEC-70","T1078.001",{"name":246,"source":236,"cwe_ids":247,"tactics":248,"capec_ids":250,"technique_id":252},"Credentials In Files",[54],[249],"credential-access",[251],"CAPEC-191","T1552.001",[],{"count":255,"next":256,"previous":6,"results":257},26,"http:\u002F\u002Fweb:8606\u002Fapi\u002Farticles\u002F?page=2&page_size=3&sorted_by=-published_at",[258,266,274],{"id":259,"title":260,"summary":261,"published_at":262,"type":263,"link":264,"image_url":265},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":267,"title":268,"summary":269,"published_at":270,"type":271,"link":272,"image_url":273},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":275,"title":276,"summary":277,"published_at":278,"type":279,"link":280,"image_url":281},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"]