We’ve given the Wallarm documentation portal a refresh, and it’s a little more than a new coat of paint.

The updated experience makes it easier to find what you need, when you need it, whether you’re getting started, digging into a specific feature, or troubleshooting in the middle of a busy day. A clearer structure helps you navigate across products with less guesswork, and our new AI-powered search gets you to relevant answers faster without ‘tab overload.’

Take the updated docs for a spin at docs.wallarm.com and see how much smoother finding answers can be.

Your API security data has a story to tell. Unfortunately, it’s been distributed across multiple tools … until now. 

Today, we’re introducing customizable API security dashboards with BI-style views that bring API traffic, attack activity, and user or account behavior together in one clear, usable place. No duct tape. No spreadsheet gymnastics. Just answers.

Every day we see teams stitching together signals from WAFs, API gateways, log platforms, and SIEMs just to answer basic questions like:

• Which APIs are under attack right now?
• Which consumers or accounts are involved?
• Is this traffic surge a business win—or a security problem?

The result? Slow investigations, inconsistent reports, and executives getting one-off summaries that don’t reliably connect API security to real business impact. That’s not a tooling problem. That’s a visibility problem.

With customizable dashboards in Wallarm, teams get ready-to-use views built directly from live API traffic, attack telemetry, and user activity.

Out of the box, dashboards include live charts for:

• API call volume and traffic trends
• Top endpoints and API consumers
• Error rates and latency patterns
• Attack counts and affected accounts

Time-range selectors and quick filters let you zoom in on exactly what matters: an incident, a single API, or a suspicious consumer. Save views for recurring questions, and export charts to PDF when it’s time to brief leadership.

These dashboards make abnormal behavior obvious and actionable. Security teams can quickly see what’s under attack and which accounts are at risk Platform teams get clarity on which endpoints need attention. Leaders get clean, repeatable summaries that actually tell the same story every time

Fewer tools to juggle. Less manual reporting. Faster, shared understanding across teams. Check out the pre-configured Security Metrics dashboard or build your own from scratch. Read more in our documentation. 

Security Edge now provides JA4 TLS client fingerprinting to identify bots and automated tools regardless of IP address or User-Agent spoofing. JA4 analyzes TLS handshake characteristics (cipher suites, extensions, supported groups) to create unique client identifiers that reveal the actual implementation, not just what the client claims to be.

Key Capabilities

• Passive extraction during TLS handshake with zero latency impact
• Threat detection for known malicious tools (Burp Suite, sqlmap, scrapers)
• Bot classification distinguishing legitimate from malicious automation
• Rate limiting by fingerprint to prevent IP-rotation attacks
• Forensic logging for audit trails and incident investigation

Use Cases

Credential Stuffing Prevention
Detect automated tools even when attackers rotate IPs and User-Agents.

API Abuse Prevention
Block scraping tools and unauthorized clients that appear as legitimate traffic.

Multi-Cloud Security
Consistent client identification across hybrid deployments regardless of network topology.

Compliance Logging
PCI-DSS compliant connection logging with forensic-grade client identification.

JA4 fingerprinting is enabled by default in Security Edge with node version 6.7.4-1 and later. For additional information, check out our documentation. 

In addition to the vulnerabilities previously published, React has disclosed new vulnerabilities affecting applications using React Server Components.

• Denial of Service (DoS) — High severity, CVSS 7.5
   CVE-2025-55184, CVE-2025-67779: Crafted requests can exhaust server resources, causing hangs or service unavailability.
  
  
• Source Code Exposure — Medium severity, CVSS 5.3
   CVE-2025-55183: Specially formed requests may lead to disclosure of server-side source code

These issues affect the same React Server Components request handling surface as React2Shell (CVE-2025-55182) but do not enable remote code execution. The previously released React2Shell fixes continue to prevent RCE, while these new vulnerabilities impact availability and confidentiality.

Recommendations:
Upgrade to the latest patched React versions and review the exposure of React Server Components endpoints.

Wallarm mitigation:
To protect customers who aren’t using blocking mode across all apps and APIs, Wallarm has rolled out a virtual patch that blocks exploitation regardless of whether customers use blocking or monitoring mode. Please contact support if you’d like to opt out.

We have introduced a new grouped view for security issues to enhance visibility and streamline analysis.

• Automatic Grouping of Similar Issues
   Security issues sharing the same title, type, risk level, and discovered-by fields are now automatically grouped into a single entry. This grouped view is enabled by default, and users can easily switch back to the atomic view using a simple toggle.
  
  
• Enhanced Issue Exploration
   Users can expand any group to view all individual issues within it, along with their affected resources and current statuses.
  
  
• No changes to existing workflows: all filters continue to operate as expected, and bulk actions remain fully supported within grouped issues.
  
  

This enhancement significantly simplifies issue triage and analysis by reducing noise and helping teams focus on patterns and trends, rather than scanning through repetitive entries.

Update: The vulnerability is being actively exploited in the wild. To protect customers who aren’t using blocking mode across all apps and APIs, we rolled out a virtual patch that blocks exploitation of CVE-2025-55182 regardless of whether customers use blocking or monitoring mode. Reach out to support if you want to opt out.

A critical flaw (CVE-2025-55182) in React Server Components was publicly disclosed together with a working PoC. We are already seeing active exploitation attempts, including early scans and payload variants.

Wallarm Protection

Wallarm provides protection against attacks leveraging this CVE out of the box. We started detecting and blocking early exploitation attempts immediately after disclosure. Additionally, Wallarm has deployed new detection rules specifically targeting malicious RSC requests and PoC-derived payload patterns.

Summary & Technical Details

The vulnerability allows attackers to send malformed RSC metadata and tampered component streams, which can lead to:

• Unauthorized access to server-side data
• Manipulation of serialized RSC payloads
• Potential remote code execution depending on application logic

Impact

Successful exploitation may result in data exposure, privilege escalation, or server-side execution in vulnerable setups.

Recommendation

Update React to the latest patched release as soon as it becomes available.

At Wallarm, we’re constantly working to deliver new capabilities and enhancements to customers. We’re pleased to announce three new features for our Security Edge customers. 

Custom Block Pages

Security Edge now supports the ability to configure custom block pages. These pages are returned in response to blocked malicious activity in addition to the 403 response. This new capability gives customers the ability to provide a branded response to blocked traffic. Read more about custom block pages in Security Edge in the documentation. 

Access Control Lists

Security Edge now supports the creation and management of Access Control Lists (ACLs) defining which IP addresses can access specific hosts and locations of your APIs. ACLs are created as part of the Security Edge configuration and apply to Security Edge nodes. Read more about ACLs in the documentation. 

Content Caching

Security Edge now supports caching rules, defining how Security Edge Inline nodes store and reuses responses from specific hosts and locations. When cache rules are configured, the system stores and reuses responses to frequent requests instead of reprocessing them, reducing load on your backend servers, lowering response times, and improving user experience. You can read more about caching rules in the documentation. 

We have introduced configurable rate limiting in AASM to give customers greater control over scan intensity and to help protect their servers from excessive load.

🔧 What’s New

AASM now enables users to define maximum request rates across several dimensions:

• Per Tenant — limits the total number of requests per second sent to a client’s entire infrastructure.
• Per Domain — limits the requests per second for each domain and its subdomains.
• Per IP — limits the requests per second sent to each IP address, helping prevent unintended overload when multiple subdomains resolve to the same host.

Rate limits can be configured in the AASM “Configure” section. By default, no RPS limitations are enforced.

💡 Important Note

Applying rate limits may increase overall scan duration, depending on the configuration.

We’ve released a number of improvements to the Schema-Based Testing capabilities within the Wallarm platform.

Broken Authentication (OWASP API2) Testing

Schema-based Testing now includes extended coverage for Broken Authentication (OWASP API2) issues in OpenAPI-based scans. The new checks help uncover common weaknesses such as missing authentication enforcement, weak token validation, JWT tampering, and exposed credentials in query strings.

Running Tests Without a Test Policy

You can now run tests without creating a predefined Test Policy. All parameters for a test run can be provided directly at runtime, allowing scans to be executed entirely from the command line. This provides greater flexibility for integrating Wallarm testing into automated workflows and CI/CD pipelines.

The capability supports both OpenAPI and Postman-based scans, and the “Generate test run command” wizard helps quickly prepare the required Docker command.

Other Updates

Additional improvements make test management more transparent and configurable.

You can now define success criteria for each test run directly in the UI, specifying the severity level of security issues that will mark a test run as failed.

New status tracking and filtering options also make it easier to monitor progress and review results efficiently.

Schema-Based Testing is available as part of Wallarm Security Testing. Read more about Schema-Based Testing in the documentation. 

Wallarm now supports OpenAPI Specification (OAS) v3.1 for API specification enforcement. 

Customers using the API specification enforcement feature in Wallarm can now upload specifications in the OAS v3.1 format. Wallarm will correctly interpret the specification format and keywords. 

Read more about specification enforcement in the documentation. OAS v3.1 support requires node 6.6.1+.