Positive Technologies Develops Dynamic Crawler for Single-Page Applications in PT BlackBox Scanner
Positive Technologies engineers have shared how they built a dynamic crawler for the PT BlackBox security scanner to handle modern single-page applications. The scanner receives an application URL and returns a list of vulnerabilities after black-box analysis. The crawler component collects the attack surface by discovering endpoints, methods, and parameters before vulnerability checks begin.
Static crawlers that only render pages and recursively extract links from the initial DOM are insufficient for SPA interfaces. In a typical React or Vue personal cabinet, clicking a profile picture reveals a submenu, settings open new tabs, and profile photo selection triggers background requests that never alter the URL. None of these elements exist in the original HTML document; they appear only after prior interactions.
The team defines a static application as one where all endpoints can be collected without interface interaction. A dynamic application requires clicks, scrolls, or text input to reveal additional endpoints and parameters. The dynamic crawler must therefore operate directly on browser state to answer two questions: which elements on the page can be interacted with, and what changes after each interaction.
Interactive elements are hard to identify from HTML alone. Handlers may be attached via addEventListener, delegated through framework root containers, or hidden inside closed shadow DOM. Conversely, visually prominent buttons may be inactive or blocked. After an interaction, the crawler must decide whether a new state has been reached by comparing observations, because URL and network activity often remain unchanged.
States are represented as sets of 64-bit fingerprints of currently enabled interactive elements. Two states are equivalent exactly when their fingerprint sets match. The URL is stored only as a possible navigation hint and does not participate in equivalence. This definition yields an equivalence relation that is reflexive, symmetric, transitive, deterministic from external page observations, and cheap to compare via hash lookup.
The crawler therefore explores the factor set of states rather than every reachable state. This keeps the number of visited classes finite and growing slower than the number of performed actions, satisfying the requirements of reproducibility, autonomy, termination, and speed needed for vulnerability scanning.
Related articles
PHP Releases Security Updates Fixing 18 Vulnerabilities Including Multiple Critical Issues
The PHP development team has published security updates addressing 18 vulnerabilities across four supported branches. Four of the flaws received a CVSSv4.0 base score of 9.2 and affect session handling functionality. CVE-2026-115560 allows unintended object injection when different session serialization formats are mixed in the same environment. CVE-2026-126714 can lead to restoration of malicious objects if a session file write operation is interrupted before completion. The updates cover PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 and were released on 19 November 2026 after an advance notice the previous day. Twelve of the issues are common to all four branches. The patches close the possibility of remote arbitrary code execution under specific conditions.
Critical PHP Vulnerability to Receive Patch on November 19 at 23:00 JST
A critical-severity vulnerability has been identified in the PHP scripting language, affecting all supported branches. The PHP security team has pre-announced a security update release scheduled for 14:00-14:30 UTC on November 19, which corresponds to 23:00-23:30 Japan Standard Time. Although the maximum severity rating is critical, the flaw does not impact default configurations and requires uncommon system setups to be exploitable. No specific technical details, CVE identifiers, or attack vectors have been disclosed ahead of the patch. The update forms part of PHP's regular four-week release cycle. This follows another serious PHP flaw called PHP2Shell that required emergency remediation in October. Organizations are strongly advised to prepare for immediate deployment once the fix becomes available.
Java4Shell Vulnerability Enables Remote Code Execution Without Authentication Across Keycloak, Jira, Confluence and Other Enterprise Platforms
A critical flaw tracked as CVE-2026-114938 and dubbed Java4Shell allows unauthenticated remote code execution on multiple widely deployed Java applications including Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate when running in their default configurations. The root cause lies in a buffer overflow inside the AVX-512-accelerated Base64 decoder of HotSpot JVM on x86-64 processors that support the VBMI instruction set. Malformed Base64 strings ending with an extra equals sign cause the decoder to write 62 or 63 bytes past the allocated output buffer before the Java runtime rejects the input. Because several authentication-related components such as Basic Auth headers, SAML artifacts and CSRF tokens are decoded before any session or access-control checks occur, the vulnerable code path executes with attacker-controlled data prior to authentication. The issue affects Java 17.0.6 and later releases on lines 21, 25 and 27 when running on Intel Xeon Ice Lake or newer and AMD Zen 4 CPUs; ARM64 systems remain unaffected. Oracle and OpenJDK released fixes on 18 November, CISA issued an urgent advisory the same day, and Amazon has already updated Corretto builds while Red Hat continues work on its distributions.
Attackers Exploit Critical Apache Roller Flaw CVE-2026-129448 for Unauthenticated Remote Code Execution
Cybercriminals are actively exploiting a critical vulnerability in Apache Roller that allows remote code execution on the server without any credentials. The Java-based blogging platform received CVE-2026-129448 with a CVSS score of 9.8, and the Apache Software Foundation has confirmed active exploitation in the wild. The attack path targets the XML-RPC endpoint, which accepts vendor extension types and deserializes requests before performing authentication. The flaw affects versions 4.0.0 through 6.1.4, expanding the scope beyond the earlier CVE-2026-82384 that only listed version 6.1.5 as affected. Disabling XML-RPC through the admin interface provides no protection on older versions because deserialization occurs before the setting is checked. The recommended fix is upgrading to version 6.1.6 or later, which properly disables extension types and enforces the configuration. Organizations unable to update immediately should set enabledForExtensions to false in web.xml or remove the XML-RPC servlet mapping.