[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"cve-CVE-2026-80517":3,"landing-trending":42,"landing-articles":122},{"id":4,"cve_id":5,"summary":6,"published":7,"cvss_data":8,"is_remote":19,"cwes":20,"cpes":22,"technologies":23,"references":24,"score":26,"epss_score":27,"epss_percentile":28,"is_kev":29,"cisa_kev_date_added":30,"cisa_kev_due_date":30,"cisa_ssvc":31,"exploits":41},399019,"CVE-2026-80517","The WP Ultimate CSV Importer  WordPress plugin before 9.2 does not properly validate the file types contained in an uploaded archive nor sanitise their content before storing them in a publicly served location, allowing high privilege users such as administrators to achieve Stored Cross-Site Scripting. On Multisite installations a site Administrator does not hold the unfiltered_html capability, so this lets them run scripts in the session of users who view the file, including Network Super Admins.","2026-10-03T06:16:00Z",{"cvss_v3.1":9},{"scope":10,"version":11,"baseScore":12,"attackVector":13,"baseSeverity":14,"vectorString":15,"integrityImpact":14,"userInteraction":16,"attackComplexity":14,"availabilityImpact":17,"privilegesRequired":18,"confidentialityImpact":14},"UNCHANGED","3.1",3.5,"NETWORK","LOW","CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:H\u002FUI:R\u002FS:U\u002FC:L\u002FI:L\u002FA:N","REQUIRED","NONE","HIGH",true,[21],"CWE-79",[],[],[25],"https:\u002F\u002Fwpscan.com\u002Fvulnerability\u002F2ac66402-2a79-42dd-9056-12c819112f07\u002F",0.38,0.00142,0.03231,false,null,{"timestamp":32,"automatable":33,"tech_impact":34,"exploitation":35,"cisa_decision":36,"cisa_remediation_timeline":40},"2026-10-03T15:06:13.562460Z","no","partial","none",{"vector":37,"decision":38,"priority":39},"CISAv1\u002FE:N\u002FA:N\u002FT:P\u002FM:H\u002F2026-10-22T22:32:29.774116\u002F","track_star","medium","60D",[],{"count":43,"next":44,"previous":30,"results":45},259,"http:\u002F\u002Fweb:8606\u002Fapi\u002Ftrending_attacks\u002F?page=2&sorted_by=-published_at",[46,58,66,73,82,89,96,100,104,113],{"id":47,"title":48,"summary":49,"published_at":50,"severity":51,"vendor":52,"products":53},258,"Multiple Vulnerabilities in Cisco Unified Communications Products - Injection & Authentication Bypass","Cisco Unified Communications Manager and its companion products (Emergency Responder, Unity Connection, IM & Presence, SME, Prime Collaboration Deployment) form Cisco's enterprise VoIP and collaboration platform, providing call control, emergency call routing, voicemail, and presence services for enterprise telephony networks.\r\n\r\nCVE-2026-76473\r\n\r\nImproper control of a resource through its lifetime (CWE-74, injection-related) in multiple Cisco voice products, including Cisco Emergency Responder, Unified CM, Unified CM IM & Presence Service, and Unity Connection. It is remotely exploitable with no privileges or user interaction required, and can result in full compromise of confidentiality, integrity, and availability (CVSS 9.8). Affected releases include Emergency Responder, Unified CM, IM & Presence, and Unity Connection versions 14 and 15 (14 through 14SU6, and 15 through 15SU4 and their maintenance releases). Cisco addressed the flaw in its October 2026 Unified Communications Products Security Hardening Release, which groups several internally discovered vulnerabilities fixed during a comprehensive security review. (Strix CVE entry, NHS Digital alert)\r\n\r\nCVE-2026-76474\r\n\r\nImproper authentication (CWE-287) affecting the same set of Cisco voice products. The flaw covers authentication bypass and session-fixication-style weaknesses; a remote, unauthenticated attacker without user interaction can fully compromise the affected system (CVSS 9.8). The same product versions are affected (Emergency Responder, Unified CM, Unified CM IM & Presence Service, and Unity Connection releases 14.x and 15.x up to 14SU6 \u002F 15SU4). It was disclosed alongside the other flaws in Cisco's October 2026 security hardening release, and customers should upgrade to the fixed hardening releases listed in the vendor advisory. (Strix CVE entry, Security Online)","2026-10-22T14:31:16.035692Z",4,"Cisco",[54,55,56,57],"Cisco Emergency Responder","Cisco Unified Communications Manager","Cisco Unity Connection","Cisco Unified CM IM & Presence Service (IM&P)",{"id":43,"title":59,"summary":60,"published_at":61,"severity":51,"vendor":62,"products":63},"Node.js (bundled Brotli) - Out-of-Bounds Write & Remote Code Execution","Node.js is a cross-platform JavaScript runtime built on V8, widely used for server-side web applications and APIs. Google Brotli is a lossless compression library whose decoder Node bundles in deps\u002Fbrotli and exposes through node:zlib; compressed HTTP responses (including Brotli Content-Encoding) are automatically decompressed by fetch() and frameworks such as Express 5.\r\n\r\nCVE-2026-111497\r\n\r\nAn out-of-bounds write in the Brotli decoder (c\u002Fdec\u002Fdecode.c) bundled with Node.js. When a Node.js process decodes a malformed Brotli-compressed stream from an attacker — for example an HTTP response body auto-decompressed via fetch(), Express 5, or node:zlib — the decoder fails to validate input boundaries and writes past buffer limits, which the Node.js project says can permit remote code execution (memory disclosure and arbitrary code execution). The same flaw exists in upstream Google Brotli versions 1.0.3 through 1.2.0. It affects the Node.js 22.x, 24.x, and 26.x release lines; end-of-life lines (e.g. 20.x, 25.x) receive no fix and are stated to be \"always affected\". Fixed in Node.js v22.23.4, v24.22.1, and v26.12.1 (October 21, 2026), based on upstream Brotli commit 0ed4268 (\"Detect and report invalid stream earlier\", Evgenii Kliuchnikov, Google). Upstream Brotli shipped fixes in 1.2.1, 1.1.1, and 1.0.10. No workaround is documented; users should upgrade Node and restart all Node processes, and rebuild any containers, single-executable apps, or appliances that bundle a Node binary. Distro packages linked against a system Brotli library depend on the distro's brotli package instead.","2026-10-22T14:08:04.199100Z","Node.js",[64,65],"Node.js runtime","Google Brotli",{"id":67,"title":68,"summary":69,"published_at":70,"severity":51,"vendor":71,"products":72},257,"Portainer - Query Parameter Confusion in Kubernetes Shell Leading to Arbitrary Command Execution in Any Pod","Portainer is a web-based container and Kubernetes management platform that provides GUI-driven administration of Docker, Swarm, and Kubernetes environments, including a browser-based kubectl shell for Kubernetes clusters managed through the Portainer Agent.\r\nGHSA-7423-r5wh-26x7\r\nImproper handling of extra parameters (CWE-235) combined with incorrect authorization (CWE-863) in the Kubernetes shell WebSocket handler (api\u002Fhttp\u002Fhandler\u002Fwebsocket\u002Fshell_pod.go). When a user opens the kubectl shell, the Portainer server creates a short-lived shell Pod and rewrites the WebSocket request to target it via the Agent's Pod-exec endpoint. The rewrite used Query().Add() to append the server-chosen namespace, podName, containerName, and command values instead of replacing them, while the Agent resolves each parameter by its first occurrence — so an authenticated standard-role user could supply duplicate query parameters and redirect the exec to any Pod and command of their choosing. On Agent-managed and Edge-Agent-managed Kubernetes environments the exec runs under the Agent's in-cluster service account, which the published manifest binds to cluster-admin, so the attacker obtains arbitrary command execution in any Pod in any namespace, full disclosure of cluster Secrets, and potential compromise of the Agent itself; Kubernetes RBAC provides no mitigation. Affected versions: >= 2.39.0 and \u003C 2.39.6 (2.39.x LTS) and all versions prior to 2.45.0, since the flawed behavior was introduced with the kubectl shell feature in 2.9.0. Fixed in 2.39.6 (LTS backport) and 2.45.0 (LTS); the 2.40–2.44 short-term support lines receive no dedicated patch. Local Kubernetes connections are not affected. Reported by D0HY30N on 2026-07-30; no CVE ID has been assigned as of publication. (Source: GitHub Security Advisory GHSA-7423-r5wh-26x7)","2026-10-22T09:12:41.197853Z","Portainer",[71],{"id":74,"title":75,"summary":76,"published_at":77,"severity":51,"vendor":78,"products":79},256,"Multiple Vulnerabilities in GitLab CE\u002FEE - Authenticated Remote Code Execution via Regular Expression Handling in CI\u002FCD Configuration","GitLab is a web-based DevOps platform providing source code management (Git repositories), CI\u002FCD pipelines, issue tracking and collaboration, widely deployed as self-managed instances (the affected configuration) in addition to GitLab's SaaS offering.\r\n\r\nCVE-2026-89078\r\n\r\nDouble free issue in GitLab's regular expression parser, exploited by supplying a specially crafted regular expression in a CI\u002FCD configuration. Under certain conditions it could allow an authenticated user to execute arbitrary code on the self-managed GitLab server. It affects GitLab CE\u002FEE versions 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1, and was patched in the September 23, 2026 critical patch release (19.2.7, 19.3.3, 19.4.1), rated 9.9 CVSS by GitLab. Reported by the same researcher (joaxcar) as the related regex-compiler flaws. (Strix, Cibersafety, The Hacker News)\r\n\r\nCVE-2026-93577\r\n\r\nInteger overflow issue in the regular expression compiler used when processing CI\u002FCD configurations: an authenticated user who causes GitLab to compile a specially crafted regular expression in a CI\u002FCD configuration could, under certain conditions, execute arbitrary code on the server. It affects the same version ranges (19.2 before 19.2.7, 19.3 before 19.3.3, 19.4 before 19.4.1) and was fixed alongside the double-free flaw in the September 23, 2026 release (19.4.1 and backports), rated 9.9 CVSS. (Strix, Mallory, IT-Connect)","2026-10-22T07:54:49.013651Z","GitLab",[80,81],"GitLab Community Edition (CE)","GitLab Enterprise Edition (EE)",{"id":83,"title":84,"summary":85,"published_at":86,"severity":51,"vendor":87,"products":88},255,"GitLab - Unauthenticated Remote Code Execution","This control is the Patrowl response to CVE-2026-110264, a critical remote code execution vulnerability in GitLab Community Edition and Enterprise Edition.\r\n\r\nPatrowl identifies every asset exposing a self-managed GitLab instance. When the version can be read, it is compared with the affected range. An asset running an affected version is reported as impacted. An asset running GitLab with an unknown version is reported as a warning. A warning means potential exposure, not a confirmed vulnerability.\r\n\r\nAbout the vulnerability. GitLab rated the flaw CVSS 10.0 and released fixes on 21 October 2026. It is an integer overflow in the regular expression compiler. Under certain conditions, an unauthenticated remote attacker can run arbitrary code on the GitLab server. GitLab has not published these conditions. No authentication is required. All versions from 7.0 are affected, which covers more than ten years of releases. \r\n\r\nGitLab.com and GitLab Dedicated are already patched. Only self-managed instances are concerned.\r\n\r\nAffected versions:\r\n- 7.0 up to 18.11.12\r\n- 19.0 up to 19.0.9\r\n- 19.1 up to 19.1.8\r\n- 19.2 up to 19.2.8\r\n- 19.3 up to 19.3.5\r\n- 19.4 up to 19.4.2\r\n- 19.5.0\r\n\r\nFirst recommendation:\r\n\r\nUpdate GitLab (only real fix). Upgrade to 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10 or 18.11.13. Start with instances reachable from the internet. Versions older than 18.11 receive no fix. They require a migration to a supported branch.\r\n\r\nReduce the exposure until the update is deployed. GitLab does not publish a workaround. If the instance cannot be updated at once, restrict access to it. Allow only your VPN or a list of trusted IP addresses. Do not leave the sign-in page open to the internet.\r\n\r\nWatch for exploitation attempts. GitLab published two detections for self-managed instances: \"Onigmo native worker crash\" and \"Org mode render error burst\". Look for them in your logs. Unexplained crashes of Puma or Sidekiq workers deserve an investigation.","2026-10-21T22:02:26.003181Z","gitlab",[87],{"id":90,"title":91,"summary":92,"published_at":93,"severity":51,"vendor":94,"products":95},250,"PHP - Remote Code Execution (Exploitation Check)","This control is the second step of the Patrowl response to CVE-2026-109618 and CVE-2026-109619, two critical remote code execution vulnerabilities in the PHP core.\r\n\r\nThe first control flagged every asset running PHP. It covered PHP itself and every technology built on it: content management systems and their plugins, e-commerce platforms, web frameworks, business applications, administration tools, hosting control panels and appliances with a PHP management interface. Those assets were reported as warnings. A warning meant potential exposure, not a confirmed vulnerability.\r\n\r\nThis control verifies the real exposure. Patrowl's team builds a dedicated detection method from the real exploitation technique. It is designed to be safe for production. It confirms whether the vulnerability can be triggered, without taking control of the server, without modifying data and without affecting the availability of the service. The method is validated on test environments before it runs on customer assets. It then runs against the assets flagged by the first control. \r\n\r\nPatrowl also publishes protection elements for vulnerable assets. They include detection and blocking rules for web application firewalls and intrusion prevention systems, and configuration changes that reduce the exposure. These measures protect the asset while the update is being deployed. They do not replace the update.\r\n\r\nAbout the vulnerabilities. The PHP project rated both flaws CVSS v4.0 9.2 and released fixes on 21 October 2026 for the 8.2, 8.3, 8.4 and 8.5 branches. An unauthenticated remote attacker can run arbitrary code on the server. The attack targets PHP itself, before any application code runs, so it cannot be fixed from within the application. Versions 8.5.11, 8.4.26, 8.3.35, 8.2.34 and earlier are affected, back to PHP 5.4 according to public reports. Versions 8.1 and older are end of life and will not receive an official fix. They require a backport from the hosting provider or Linux distribution, or a migration to a supported branch.","2026-10-21T08:10:50.202864Z","php",[94],{"id":97,"title":91,"summary":98,"published_at":93,"severity":51,"vendor":94,"products":99},252,"This control is the second step of the Patrowl response to CVE-2026-109618 and CVE-2026-109619, two critical remote code execution vulnerabilities in the PHP core.\r\n\r\nThe first control flagged every asset running PHP. It covered PHP itself and every technology built on it: content management systems and their plugins, e-commerce platforms, web frameworks, business applications, administration tools, hosting control panels and appliances with a PHP management interface. Those assets were reported as warnings. A warning meant potential exposure, not a confirmed vulnerability.\r\n\r\nThis control verifies the real exposure. Patrowl's team builds a dedicated detection method from the real exploitation technique. It is designed to be safe for production. It confirms whether the vulnerability can be triggered, without taking control of the server, without modifying data and without affecting the availability of the service. The method is validated on test environments before it runs on customer assets. It then runs against the assets flagged by the first control. \r\n\r\nPatrowl also publishes protection elements for vulnerable assets. They include detection and blocking rules for web application firewalls and intrusion prevention systems, and configuration changes that reduce the exposure. These measures protect the asset while the update is being deployed. They do not replace the update.\r\n\r\nAbout the vulnerabilities. The PHP project rated both flaws CVSS v4.0 9.2 and released fixes on 21 October 2026 for the 8.2, 8.3, 8.4 and 8.5 branches. An unauthenticated remote attacker can run arbitrary code on the server. The attack targets PHP itself, before any application code runs, so it cannot be fixed from within the application. Versions 8.5.11, 8.4.26, 8.3.35, 8.2.34 and earlier are affected, back to PHP 5.4 according to public reports. Versions 8.1 and older are end of life and will not receive an official fix. They require a backport from the hosting provider or Linux distribution, or a migration to a supported branch.\r\n\r\n\r\nUpdated : First recommendation : \r\n1. Patch the runtime (only real fix). Update to the emergency release for your branch from php.net or your distro, internet-facing servers first. Verify no PHP 5\u002F7\u002F8.0–8.1 remains; if it does and cannot be upgraded, isolate it (VPN, deny-all, or WAF-only exposure) immediately.\r\n\r\n2. Disable session upload progress (defense in depth, also blocks known PoCs):\r\n\r\n`session.upload_progress.enabled = Off`\r\n\r\n3. Deploy interim WAF rules (mitigation only, not a patch):\r\nCloudflare: emergency rules released 21 Oct in Managed and Free Rulesets (\"Generic Rules - Anomalous Execution\"). Ensure your origin is not directly reachable (allow only Cloudflare IPs).\r\n\r\nModSecurity (v2, Apache 2.4, tested):\r\n```\r\nSecRule ARGS_POST_NAMES \"@streq PHP_SESSION_UPLOAD_PROGRESS\" \\\r\n  \"id:1026109618,phase:2,deny,status:403,log,t:none,msg:'PHP session upload progress field (interim, PHP CVE-2026-109618\u002F109619)'\r\n```\r\n\r\n\"Requires SecRequestBodyAccess On; adjust the field name if session.upload_progress.name is non-default.\r\n\r\n4. If possible, Reject or restrict multipart\u002Fform-data POSTs on routes with no legitimate upload workflow; rate-limit large multipart posts. Do not blanket-block without testing (breaks document uploads and some APIs).\r\n\r\n5. Wait for Patrowl's diagnostic",[94],{"id":101,"title":91,"summary":102,"published_at":93,"severity":51,"vendor":94,"products":103},254,"This control is the second step of the Patrowl response to CVE-2026-109618 and CVE-2026-109619, two critical remote code execution vulnerabilities in the PHP core.\r\n\r\nThe first control flagged every asset running PHP. It covered PHP itself and every technology built on it: content management systems and their plugins, e-commerce platforms, web frameworks, business applications, administration tools, hosting control panels and appliances with a PHP management interface. Those assets were reported as warnings. A warning meant potential exposure, not a confirmed vulnerability.\r\n\r\nThis control verifies the real exposure. Patrowl's team builds a dedicated detection method from the real exploitation technique. It is designed to be safe for production. It confirms whether the vulnerability can be triggered, without taking control of the server, without modifying data and without affecting the availability of the service. The method is validated on test environments before it runs on customer assets. It then runs against the assets flagged by the first control. \r\n\r\nPatrowl also publishes protection elements for vulnerable assets. They include detection and blocking rules for web application firewalls and intrusion prevention systems, and configuration changes that reduce the exposure. These measures protect the asset while the update is being deployed. They do not replace the update.\r\n\r\nAbout the vulnerabilities. The PHP project rated both flaws CVSS v4.0 9.2 and released fixes on 21 October 2026 for the 8.2, 8.3, 8.4 and 8.5 branches. An unauthenticated remote attacker can run arbitrary code on the server. The attack targets PHP itself, before any application code runs, so it cannot be fixed from within the application. Versions 8.5.11, 8.4.26, 8.3.35, 8.2.34 and earlier are affected, back to PHP 5.4 according to public reports. Versions 8.1 and older are end of life and will not receive an official fix. They require a backport from the hosting provider or Linux distribution, or a migration to a supported branch.\r\n\r\n\r\nUpdated: First recommendation:\r\n\r\nPatch the runtime (only real fix). Update to 8.2.35, 8.3.36, 8.4.27 or 8.5.12 from php.net, or to your distro’s backported package. Start with internet-facing servers, Apache mod_php first. Then restart every PHP process (Apache, PHP-FPM master and pools), or old workers keep running vulnerable code. Verify no PHP 5\u002F7\u002F8.0–8.1 remains. If it does and cannot be upgraded, isolate it immediately (VPN, deny-all, or WAF-only exposure).\r\nDisable risky PHP features (defense in depth, partial). Set these in php.ini or with php_admin_flag \u002F php_admin_value, then restart all workers:\r\nsession.upload_progress.enabled = Off\r\nfatal_error_backtraces = Off   ; PHP 8.5 only\r\n\r\nTogether they remove the two confirmed exploitation paths of CVE-2026-109619. They do not mitigate CVE-2026-109618.\r\n\r\nDeploy interim WAF rules (mitigation only, not a patch).\r\n\r\nCloudflare: emergency rules released 21 Oct in Managed and Free Rulesets (“Generic Rules - Anomalous Execution”). Ensure your origin is not directly reachable (allow only Cloudflare IPs).\r\n\r\nModSecurity (v2, Apache 2.4, tested):\r\n\r\nSecRule ARGS_POST_NAMES \"@streq PHP_SESSION_UPLOAD_PROGRESS\" \\\r\n  \"id:1026109618,phase:2,deny,status:403,log,t:none,msg:'PHP session upload progress field (interim, PHP CVE-2026-109619)'\"\r\n\r\nRequires SecRequestBodyAccess On. Adjust the field name if session.upload_progress.name is non-default. This rule only covers CVE-2026-109619.\r\n\r\nRestrict multipart\u002Fform-data (main interim measure for CVE-2026-109618). The attack exhausts PHP memory with crafted multipart requests.\r\nReject multipart\u002Fform-data POSTs on routes with no legitimate upload workflow.\r\nReject multipart requests without a Content-Length header.\r\nCap the body size at the proxy or WAF and rate-limit large multipart posts.\r\nIn PHP, keep post_max_size conservative and lower max_input_vars, max_input_nesting_level and max_file_uploads.\r\nDo not blanket-block without testing: it breaks document uploads and some APIs.\r\nWait for Patrowl’s diagnostic.",[94],{"id":105,"title":106,"summary":107,"published_at":108,"severity":51,"vendor":109,"products":110},251,"Dolibarr - Remote Code Execution via dol_eval_standard() Sandbox Bypass & SSRF & Arbitrary File Read","Dolibarr is an open-source ERP\u002FCRM suite written in PHP, widely used by small and medium businesses for invoicing, accounting, customers, products, and inventory management.\r\n\r\nGHSA-5cfw-655w-vqp8 (no CVE assigned yet)\r\n\r\nA sandbox bypass in dol_eval_standard() (in core\u002Flib\u002Ffunctions.lib.php) allows an authenticated administrator to achieve Remote Code Execution by creating a malicious computed extrafield. The whitelist path fails to block three things: unrestricted class instantiation (only ReflectionFunction is blocked, so dangerous built-ins like PDO, SQLite3, SimpleXMLElement, SplFileObject can be instantiated); PHP's callable array syntax ([$object, \"method\"])(), which evades the function-call whitelist regex and the )( forbidden-string check that is only enforced in the blacklist path; and SQLite's char()\u002Fhex blob functions, which construct \u003C?php strings without the literal \u003C character. The full chain creates a SQLite database file with a .php extension in the webroot (htdocs\u002Fcustom\u002F, writable by default) containing a webshell, which is then executed by PHP when requested over HTTP. Even without a file write, new SimpleXMLElement() enables SSRF to internal networks and cloud metadata services, and arbitrary file read via XXE (including database credentials in conf\u002Fconf.php). Although setup requires admin privileges, the computed field is evaluated in the context of every user who views an affected record, giving a malicious or compromised admin persistent RCE on the entire server. Affected versions are ≤ 23.0.0 (23.0.0 confirmed; likely all versions using dol_eval_standard() with the default whitelist path). Fixed in version 23.0.3. CWE-94. Discovered and reported by Grzegorz Tworek (F3715H, sec4check) in March 2026.","2026-10-21T08:01:07.843181Z","Dolibarr",[111,112],"Dolibarr ERP","Dolibarr CRM",{"id":114,"title":115,"summary":116,"published_at":117,"severity":118,"vendor":119,"products":120},249,"Next.js - Server-Side Request Forgery","Next.js is a React-based web framework for building server-rendered and static web applications. Its Image Optimization feature fetches remote images allowed by the `images.remotePatterns` setting and resizes them on demand.\r\n\r\nCVE-2026-94483\r\n\r\nFrom 16.0.0 until 16.3.8, Image Optimization can follow attacker-controlled DNS resolution for a remote URL that matches `images.remotePatterns`. The optimized image fetch can then reach private IP addresses after the URL has passed the allow-list check (Server-Side Request Forgery, CWE-918). The CVSS 4.0 vector rates confidentiality impact High and integrity impact Low. Applications without `images.remotePatterns` are not affected. Affected versions are >= 16.0.0 and \u003C 16.3.8. The fix is in 16.3.8. Users who cannot upgrade should audit allow-listed hosts and avoid entries whose DNS records are not trusted. CISA ADP SSVC lists exploitation as none, automatable as no, and technical impact as partial. One third-party tracker reports a public proof-of-concept. The CVE is not in the CISA KEV catalog. Published October 2, 2026.","2026-10-21T07:47:12.806019Z",2,"Vercel",[121],"Next.js",{"count":123,"next":124,"previous":30,"results":125},30,"http:\u002F\u002Fweb:8606\u002Fapi\u002Farticles\u002F?page=2&sorted_by=-published_at",[126,133,141,149,156,163,170,175,182,189],{"id":123,"title":127,"summary":128,"published_at":129,"type":130,"link":131,"image_url":132},"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":134,"title":135,"summary":136,"published_at":137,"type":138,"link":139,"image_url":140},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":142,"title":143,"summary":144,"published_at":145,"type":146,"link":147,"image_url":148},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",{"id":150,"title":151,"summary":152,"published_at":153,"type":138,"link":154,"image_url":155},27,"Exposure Management: definition, stakes, and how it works","Vulnerabilities, misconfigurations, poorly managed identities: understand what Exposure Management is and why it matters in 2026.","2026-09-10T00:00:00Z","https:\u002F\u002Fpatrowl.io\u002Fen\u002Fblog\u002Fdefinition-exposure-management","https:\u002F\u002Fpatrowl.io\u002Fmedia\u002Fsite\u002F06170638a9-1789050834\u002Fexposure.management.definition.en.png",{"id":157,"title":158,"summary":159,"published_at":160,"type":146,"link":161,"image_url":162},26,"DGFiP Cyberattack 2026: Inside the Attacker","Two distinct attacks hit France","2026-08-17T00:00:00Z","https:\u002F\u002Fpatrowl.io\u002Fen\u002Fblog\u002Fdgfip-cyberattack-2026-inside-attacker-mind","https:\u002F\u002Fpatrowl.io\u002Fmedia\u002Fsite\u002Fdc38d33696-1787055371\u002Fdgfip-2026.png",{"id":164,"title":165,"summary":166,"published_at":167,"type":130,"link":168,"image_url":169},25,"CVE-2026-64638: XSS2Shell, a WordPress Login Vulnerability","Pre-auth XSS on wp-login.php, patched August 6. What is actually exploitable, and how to read it in your Patrowl report.","2026-08-10T00:00:00Z","https:\u002F\u002Fpatrowl.io\u002Fen\u002Fblog\u002Fxss2shell-critical-wordpress-login-vulnerability-2026","https:\u002F\u002Fpatrowl.io\u002Fmedia\u002Fsite\u002F904e61748b-1786369212\u002Fxss2shell.png",{"id":171,"title":172,"summary":172,"published_at":167,"type":130,"link":173,"image_url":174},24,"CVE-2026-64638 : XSS2Shell, faille du login WordPress","https:\u002F\u002Fpatrowl.io\u002Fen\u002Fblog\u002Fcve-2026-64638-xss2shell-faille-login-wordpress","",{"id":176,"title":177,"summary":178,"published_at":179,"type":130,"link":180,"image_url":181},23,"How Agentic AI Hunts Down CVEs Before Attackers Do","38 vulnerability sources monitored around the clock, pentester-validated proof of exploitability, an alert within hours. See how it works.","2026-08-05T00:00:00Z","https:\u002F\u002Fpatrowl.io\u002Fen\u002Fblog\u002Fproactive-threat-hunting-agentic-ai-cve","https:\u002F\u002Fpatrowl.io\u002Fmedia\u002Fsite\u002F804988ce7b-1785930160\u002Fproactive-threat-hunting-how-agentic-ai-tracks-cves.png",{"id":183,"title":184,"summary":185,"published_at":186,"type":146,"link":187,"image_url":188},22,"AI Agent Incident: OpenAI HuggingFace — Risks and Lessons","An autonomous AI agent escaped its sandbox via a JFrog Artifactory zero-day, compromised HuggingFace via privilege escalation and stolen credentials. Reconstructed timeline and security lessons.","2026-07-31T00:00:00Z","https:\u002F\u002Fpatrowl.io\u002Fen\u002Fblog\u002Fai-agent-incident-openai-huggingface-risks","[Image URL from Kirby]",{"id":190,"title":191,"summary":192,"published_at":193,"type":138,"link":194,"image_url":195},21,"SaaS Under Watch: What Your SDLC Doesn","Your pipeline is green. Your real exposure may have changed without you knowing it. The complete guide for software vendors.","2026-07-29T00:00:00Z","https:\u002F\u002Fpatrowl.io\u002Fen\u002Fblog\u002Fsecuring-saas-application-software-vendor","https:\u002F\u002Fpatrowl.io\u002Fmedia\u002Fsite\u002F20d6ec0cd0-1785331401\u002Fapplication-security.png"]