[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"landing-trending":3,"cve-CVE-2019-5999":30,"landing-articles":338},{"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":51,"cwes":52,"cpes":54,"technologies":187,"references":320,"score":326,"epss_score":327,"epss_percentile":328,"is_kev":51,"cisa_kev_date_added":6,"cisa_kev_due_date":6,"cisa_ssvc":329,"attack_mappings":335,"exploits":336},235522,"CVE-2019-5999","EUVD-2019-15567","Buffer overflow in PTP (Picture Transfer Protocol) of EOS series digital cameras (EOS-1D X firmware version 2.1.0 and earlier, EOS-1D X MKII firmware version 1.1.6 and earlier, EOS-1D C firmware version 1.4.1 and earlier, EOS 5D MARK III firmware version 1.3.5 and earlier, EOS 5D MARK IV firmware version 1.2.0 and earlier, EOS 5DS firmware version 1.1.2 and earlier, EOS 5DS R firmware version 1.1.2 and earlier, EOS 6D firmware version 1.1.8 and earlier, EOS 6D MARK II firmware version 1.0.4 and earlier, EOS 7D MARK II firmware version 1.1.2 and earlier, EOS 70 D firmware version 1.1.2 and earlier, EOS 80 D firmware version 1.0.2 and earlier, EOS KISS X7I \u002F EOS D REBEL T5I \u002F EOS 700D firmware version 1.1.5 and earlier, EOS KISS X8I \u002F EOS D REBEL T6I \u002F EOS 750D firmware version 1.0.0 and earlier, EOS KISS X9I \u002F EOS D REBEL T7I \u002F EOS 800D firmware version 1.0.1 and earlier, EOS KISS X7 \u002F EOS D REBEL SL1 \u002F EOS 100D firmware version 1.0.1 and earlier, EOS KISS X9 \u002F EOS D REBEL SL2 \u002F EOS 200D firmware version 1.0.1 and earlier, EOS KISS X10 \u002F EOS D REBEL SL3 \u002F EOS 200D \u002F EOS 250D firmware version 1.0.1 and earlier, EOS 8000D \u002F EOS D REBEL T6S \u002F EOS 760D firmware version 1.0.0 and earlier, EOS 9000D \u002F EOS 77D firmware version 1.0.2 and earlier, EOS KISS X70 \u002F EOS D REBEL T5 \u002F EOS 1200D firmware version 1.0.2 and earlier, EOS D REBEL T5 RE \u002F EOS 1200D MG \u002F EOS HI firmware version 1.0.2 and earlier, EOS KISS X80 \u002F EOS D REBEL T6 \u002F EOS 1300D firmware version 1.1.0 and earlier, EOS KISS X90 \u002F EOS D REBEL T7 \u002F EOS 1500D \u002F EOS 2000D firmware version 1.0.0 and earlier, EOS D REBEL T100 \u002F EOS 3000D \u002F EOS 4000D firmware version 1.0.0 and earlier, EOS R firmware version 1.3.0 and earlier, EOS RP firmware version 1.2.0 and earlier, EOS RP GOLD firmware version 1.2.0 and earlier, EOS M2 firmware version 1.0.3 and earlier, EOS M3 firmware version 1.2.0 and earlier, EOS M5 firmware version 1.0.1 and earlier, EOS M6 firmware version 1.0.1 and earlier, EOS M6(China) firmware version 5.0.0 and earlier, EOS M10 firmware version 1.1.0 and earlier, EOS M100 firmware version 1.0.0 and earlier, EOS KISS M \u002F EOS M50 firmware version 1.0.2 and earlier) and PowerShot SX740 HS firmware version 1.0.1 and earlier, PowerShot SX70 HS firmware version 1.1.0 and earlier, and PowerShot G5Xmark II firmware version 1.0.1 and earlier allows an attacker on the same network segment to trigger the affected product being unresponsive or to execute arbitrary code on the affected product via blerequest command.","2019-08-06T19:15:00Z",{"cvss_v2.0":37,"cvss_v3.0":45},{"version":38,"baseScore":39,"accessVector":40,"vectorString":41,"authentication":42,"integrityImpact":43,"accessComplexity":44,"availabilityImpact":43,"confidentialityImpact":43},"2.0",8.3,"ADJACENT_NETWORK","AV:A\u002FAC:L\u002FAu:N\u002FC:C\u002FI:C\u002FA:C","NONE","COMPLETE","LOW",{"scope":46,"version":47,"baseScore":48,"attackVector":40,"baseSeverity":49,"vectorString":50,"integrityImpact":49,"userInteraction":42,"attackComplexity":44,"availabilityImpact":49,"privilegesRequired":42,"confidentialityImpact":49},"UNCHANGED","3.0",8.8,"HIGH","CVSS:3.0\u002FAV:A\u002FAC:L\u002FPR:N\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H",false,[53],"CWE-787",[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],"cpe:2.3:h:canon:eos_70d:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_m100_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_kiss_x9i_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_77d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_kiss_m:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_4000d:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_d_rebel_t100:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_m10_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:powershot_g5xmark_ii_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_100d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_6d:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_5ds_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:powershot_sx70_hs_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:powershot_g5xmark_ii:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_kiss_x70:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_5ds_r:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos-1d_c:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_m10:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos-1d_x_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_1300d:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_d_rebel_t7:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_d_rebel_t7_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_m6_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_r:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_1200d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_d_rebel_t5:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_1200d_mg:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_760d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_kiss_x7:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_d_rebel_t5i_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_5ds_r_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_8000d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_5ds:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_rp_gold:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_9000d:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_kiss_x9:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:powershot_sx70_hs:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_80d:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_m3:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_d_rebel_sl3_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_m6\\(china\\)_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos-1d_x_mkii_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_kiss_x7i:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_d_rebel_t7i_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_2000d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_d_rebel_t100_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_6d_mark_ii_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_hi_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_kiss_x10:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_d_rebel_t6s:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos-1d_c_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_200d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_d_rebel_t6i:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_m2_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_1200d_mg_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_m6\\(china\\):-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_5d_mark_iv:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_750d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_d_rebel_t6_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_7d_mark_ii_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_d_rebel_sl2_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_d_rebel_t7i:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_70d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_1500d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_kiss_x80:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_3000d:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_kiss_x7_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_d_rebel_t5_re:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_1300d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_m50_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_rp_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_kiss_x8i_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_1500d:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_d_rebel_t5i:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:powershot_sx740_hs_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_rp_gold_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_kiss_x7i_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_m5:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_5d_mark_iii_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_100d:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_800d:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_rp:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_m3_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_5d_mark_iii:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_8000d:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_800d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_1200d:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_250d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_m2:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_6d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_kiss_x70_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:powershot_sx740_hs:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_4000d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_d_rebel_t6i_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_kiss_x9_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_hi:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_760d:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_m100:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_d_rebel_t6:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_d_rebel_sl2:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_m5_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_kiss_m_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_kiss_x10_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_d_rebel_t5_re_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos-1d_x_mkii:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_kiss_x90:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_kiss_x80_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_m6:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_d_rebel_t5_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_r_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_kiss_x9i:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_d_rebel_sl1_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_3000d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_m50:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_700d:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_6d_mark_ii:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_80d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos-1d_x:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_9000d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_200d:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_250d:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_kiss_x90_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_77d:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_d_rebel_sl1:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_700d_firmware:*:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_5d_mark_iv_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_750d:-:*:*:*:*:*:*:*","cpe:2.3:o:canon:eos_d_rebel_t6s_firmware:*:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_kiss_x8i:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_2000d:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_d_rebel_sl3:-:*:*:*:*:*:*:*","cpe:2.3:h:canon:eos_7d_mark_ii:-:*:*:*:*:*:*:*",[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,292,293,294,295,296,297,298,299,300,301,302,303,304,305,306,307,308,309,310,311,312,313,314,315,316,317,318,319],"Canon Eos Hi Firmware","Canon Eos M50","Canon Eos M100 Firmware","Canon Eos 9000D","Canon Eos Kiss X10","Canon Eos 1200D Firmware","Canon Eos D Rebel Sl2","Canon Eos 1500D Firmware","Canon Eos M10 Firmware","Canon Eos Kiss X10 Firmware","Canon Eos 4000D Firmware","Canon Eos M10","Canon Eos 5D Mark Iv Firmware","Canon Powershot G5Xmark Ii","Canon Eos-1D X Mkii Firmware","Canon Powershot Sx70 Hs","Canon Eos D Rebel T6I","Canon Powershot Sx740 Hs","Canon Powershot G5Xmark Ii Firmware","Canon Eos Kiss X7I Firmware","Canon Eos Hi","Canon Eos M5 Firmware","Canon Eos D Rebel T5I Firmware","Canon Eos Kiss X80 Firmware","Canon Eos D Rebel T6 Firmware","Canon Eos 760D Firmware","Canon Eos D Rebel T5 Firmware","Canon Eos Kiss X9","Canon Eos Kiss M","Canon Eos D Rebel T5I","Canon Eos Rp Firmware","Canon Eos D Rebel Sl2 Firmware","Canon Eos 1500D","Canon Eos-1D X","Canon Eos Kiss X80","Canon Eos 2000D Firmware","Canon Eos D Rebel Sl3 Firmware","Canon Eos Kiss X7 Firmware","Canon Eos 7D Mark Ii","Canon Eos 77D","Canon Eos 5D Mark Iii","Canon Eos 100D","Canon Eos Kiss X70","Canon Eos 700D","Canon Eos 800D","Canon Eos 2000D","Canon Eos Kiss X7","Canon Eos M6 Firmware","Canon Eos D Rebel Sl1","Canon Eos 77D Firmware","Canon Eos 1200D Mg Firmware","Canon Eos D Rebel T5 Re Firmware","Canon Eos D Rebel Sl1 Firmware","Canon Eos D Rebel T6S Firmware","Canon Eos D Rebel T7 Firmware","Canon Eos Rp Gold Firmware","Canon Eos D Rebel T6","Canon Eos Kiss X7I","Canon Eos 8000D Firmware","Canon Eos 3000D Firmware","Canon Eos M5","Canon Eos D Rebel T100","Canon Eos 5D Mark Iv","Canon Eos 750D","Canon Eos D Rebel T6S","Canon Eos M50 Firmware","Canon Eos 6D","Canon Eos 70D","Canon Eos 200D","Canon Eos 8000D","Canon Eos 5Ds","Canon Eos Kiss X90 Firmware","Canon Eos M6","Canon Eos 6D Mark Ii","Canon Eos Kiss X9 Firmware","Canon Eos 80D","Canon Eos D Rebel Sl3","Canon Eos Rp Gold","Canon Powershot Sx70 Hs Firmware","Canon Eos R Firmware","Canon Eos 700D Firmware","Canon Eos 1200D","Canon Eos-1D C Firmware","Canon Eos 800D Firmware","Canon Eos 750D Firmware","Canon Eos 5Ds R","Canon Eos D Rebel T7I","Canon Eos 5Ds Firmware","Canon Eos 1200D Mg","Canon Eos D Rebel T5 Re","Canon Eos-1D X Firmware","Canon Eos 760D","Canon Eos 6D Firmware","Canon Eos 1300D","Canon Eos M3 Firmware","Canon Eos 5D Mark Iii Firmware","Canon Eos 6D Mark Ii Firmware","Canon Eos 3000D","Canon Eos 9000D Firmware","Canon Eos 5Ds R Firmware","Canon Eos M3","Canon Eos Kiss X9I","Canon Eos-1D X Mkii","Canon Eos 7D Mark Ii Firmware","Canon Eos Kiss X90","Canon Eos 70D Firmware","Canon Eos 80D Firmware","Canon Eos Kiss M Firmware","Canon Eos D Rebel T6I Firmware","Canon Eos 4000D","Canon Eos R","Canon Eos Kiss X9I Firmware","Canon Eos 250D Firmware","Canon Eos Kiss X8I","Canon Eos Kiss X70 Firmware","Canon Eos 1300D Firmware","Canon Eos M100","Canon Eos D Rebel T7I Firmware","Canon Eos D Rebel T5","Canon Eos 250D","Canon Eos M6\\(China\\)","Canon Powershot Sx740 Hs Firmware","Canon Eos 100D Firmware","Canon Eos 200D Firmware","Canon Eos Rp","Canon Eos M6\\(China\\) Firmware","Canon Eos D Rebel T7","Canon Eos M2 Firmware","Canon Eos M2","Canon Eos Kiss X8I Firmware","Canon Eos-1D C","Canon Eos D Rebel T100 Firmware",[321,322,323,324,325],"http:\u002F\u002Fjvn.jp\u002Fen\u002Fvu\u002FJVNVU97511331\u002Findex.html","https:\u002F\u002Fcweb.canon.jp\u002Fe-support\u002Fproducts\u002Feos-d\u002F190806dilc-firm.html","https:\u002F\u002Fresearch.checkpoint.com\u002Fsay-cheese-ransomware-ing-a-dslr-camera\u002F","https:\u002F\u002Fwww.canon-europe.com\u002Fsupport\u002Fproduct-security\u002F","https:\u002F\u002Fwww.usa.canon.com\u002Finternet\u002Fportal\u002Fus\u002Fhome\u002Fsupport\u002Fproduct-advisories\u002Fdetail\u002Fthe-vulnerability-in-canon-digital-cameras",0.59,0.02459,0.84318,{"timestamp":6,"automatable":330,"tech_impact":331,"exploitation":332,"cisa_decision":333,"cisa_remediation_timeline":334},"no","partial","none",{},"FSU",[],[337],{"link":323},{"count":339,"next":340,"previous":6,"results":341},26,"http:\u002F\u002Fweb:8606\u002Fapi\u002Farticles\u002F?page=2&page_size=3&sorted_by=-published_at",[342,350,358],{"id":343,"title":344,"summary":345,"published_at":346,"type":347,"link":348,"image_url":349},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":351,"title":352,"summary":353,"published_at":354,"type":355,"link":356,"image_url":357},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":359,"title":360,"summary":361,"published_at":362,"type":363,"link":364,"image_url":365},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"]