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
CISA Adds Three Actively Exploited Linux Kernel Vulnerabilities to KEV Catalog
The U.S. Cybersecurity and Infrastructure Security Agency has added three vulnerabilities affecting the Linux Kernel to its Known Exploited Vulnerabilities catalog. The flaws, identified as CVE-2025-39682, CVE-2026-53266, and CVE-2025-39964, are confirmed to be under active exploitation in the wild. CISA is directing all federal agencies to apply patches immediately and to search for indicators of compromise. The vulnerabilities impact the kernel's kTLS TLS processing, the ebtables network bridge component, and the AF_ALG cryptographic interface. Each issue can lead to memory corruption or inconsistent internal state that attackers may leverage for privilege escalation or remote code execution.
Keycloak Cluster on Three VMs: Engineers Detail Embedded Infinispan Setup, HA Testing Failures, and Bug Fix
A team deployed Keycloak for 25,000–30,000 users across a country using three isolated VMs instead of Kubernetes. They chose Embedded Infinispan with JGroups over an external cluster to reduce failure points and maintain session replication. PostgreSQL with Patroni handled shared storage and JDBC_PING discovery. Testing revealed that full datacenter outages triggered split-brain conditions and 5xx errors that the built-in healthcheck could not resolve. The engineers wrote a Python watcher script to detect multiple coordinators in the JGROUPS_PING table and restart affected containers. They reported the recovery bug to the Keycloak project, which was confirmed and fixed in a later release. The production cluster now survives single-DC loss without session loss.
From UDP Probe to Working Tunnel: Analyzing Hysteria2 Behavior via QUIC, HTTP/3 and Client Events
A detailed technical study examined how commercial Hysteria2 VPN endpoints respond to different levels of network probing, starting from simple UDP packets and progressing to full QUIC handshakes and authenticated client connections. The research used custom NetProbe tools on Windows and Linux to test real subscription endpoints, capturing both external probe results and decrypted traffic from an instrumented Hysteria2 client. Simple UDP probes received no response and timed out, while properly formed QUIC Initial packets with TLS ClientHello and ALPN h3 successfully completed handshakes using TLS 1.3 and TLS_AES_256_GCM_SHA384. An unauthenticated HTTP/3 GET request triggered immediate connection closure with H3_NO_ERROR (code 0x100), whereas a legitimate client sending POST /auth with Hysteria-Auth headers received the expected 233 status confirming authentication and UDP forwarding support. Subsequent data transfer tests, including parallel requests and file downloads, were observed inside separate QUIC streams after authentication, confirming that the tunnel carried real traffic. The study highlights differences between external probing and authenticated client behavior, providing practical insight into how Hysteria2 servers handle reconnaissance versus legitimate VPN usage.
Unbound 1.26.1 Patches Critical DNSSEC Validator Flaw CVE-2026-81642 Enabling Remote Code Execution
NLnet Labs has released Unbound 1.26.1 to address CVE-2026-81642, a critical vulnerability in the DNSSEC validator that can cause service crashes and potential remote code execution. The flaw affects all versions up to and including 1.26.0 and is triggered when validating a malicious DNS zone. It resides in the handling of DNSKEY records, where a buffer overflow can occur during DNS response processing. The vulnerability carries a CVSS 4.0 score of 9.1 with a network attack vector, no privileges required, and no user interaction needed. Exploitation requires an attacker to control a malicious DNS zone that the resolver queries, which can lead to denial of service or RCE in the worst case. The update also includes fixes for eight additional security issues, including CVE-2026-82717 and CVE-2026-81634, both involving heap corruption.