Loading story…
Researchers disclosed critical pre-authentication remote code execution flaws in ForgeRock/OpenAM that let attackers execute code without logging in by abusing unsafe Java deserialization in request parameters. PortSwigger reported CVE-2021-35464 in ForgeRock OpenAM, while later research detailed CVE-2026-33439 in OpenIdentityPlatform OpenAM, where attacker-controlled data in the jato.clientSession parameter could reach ApplicationObjectInputStream.readObject() without class filtering.
The newer flaw affected unauthenticated password-reset endpoints including /openam/ui/PWResetUserValidation and /openam/ui/PWResetQuestion, where JSP processing of <jato:form> tags exposed the vulnerable code path. Researchers said a crafted gadget chain could achieve code execution with a single GET request on OpenAM 16.0.5, and that version 16.0.6 fixed the issue by routing Encoder.deserialize() through the same whitelist-based deserialization protections previously applied to jato.pageSession; the bug was assigned CVSS 9.8 and mapped to CWE-502.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
3 events from the most recent confirmed update back to the earliest known activity.
The disclosure states that OpenAM 16.0.6 fixes CVE-2026-33439 by routing Encoder.deserialize() through the same whitelist-based deserialization logic already used for jato.pageSession.
Hacktron disclosed CVE-2026-33439, a critical pre-authentication RCE in OpenIdentityPlatform OpenAM caused by unsafe deserialization of the jato.clientSession parameter on unauthenticated password reset pages. The write-up states the issue was tested on OpenAM 16.0.5 and can be exploited with a single GET request.
PortSwigger Research published details of a pre-authentication remote code execution vulnerability in ForgeRock OpenAM tracked as CVE-2021-35464.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Researchers disclosed multiple **BMC FootPrints ITSM** vulnerabilities that can be chained to achieve **pre-authenticated remote code execution**, highlighting the product as a high-value target because ITSM platforms often contain asset inventories, incident data, configuration details, and other operationally sensitive information. *watchTowr Labs* said it found and chained flaws in 2025 against what was then a fully patched deployment, while broader reporting noted a set of four issues affecting the platform and framed the exposure as part of a wider pattern of attackers abusing enterprise management software. A related disclosure, **CVE-2025-71260**, affects BMC FootPrints versions `20.20.02` through `20.24.01.001` and stems from unsafe ASP.NET `VIEWSTATE` deserialization, allowing an authenticated attacker to execute arbitrary code and fully compromise the application. The vendor has issued hotfixes for affected releases, but the references do not all describe the exact same exploit chain: the watchTowr research focuses on **pre-auth RCE chains**, while the CVE entry covers a specific **authenticated** deserialization bug, making it adjacent but not fully the same incident thread.
Jun 29, 2026
A **maximum-severity authentication bypass** was disclosed in *pac4j*’s JWT component (*pac4j-jwt*), tracked as **CVE-2026-29000**, affecting a widely used Java security engine embedded across many downstream software packages. The issue is a **logic flaw** that enables attackers to bypass authentication controls by crafting tokens/claims in a way that defeats expected verification, raising concern because exploitation can be relatively straightforward and the library’s transitive use complicates exposure tracking and patch rollout across dependent applications. Public **proof-of-concept (PoC)** code is available, and reporting indicates an attacker who can obtain a target server’s **RSA public key** (often publicly accessible) can forge a **JWE-wrapped PlainJWT** containing arbitrary `sub` and role claims to bypass signature verification and authenticate as any user, including administrators. The pac4j maintainer disclosed the defect and released patched versions shortly after private reporting; while there were no confirmed in-the-wild exploits at the time of reporting, defenders should expect downstream vendors and application owners to issue their own advisories and updates as they assess inherited risk from bundled pac4j versions.
Jun 29, 2026
Several open source projects disclosed serious vulnerabilities affecting developer and infrastructure tooling, including remote code execution, SQL injection, server-side request forgery, prompt-driven query injection, and path traversal. **Coder Workspace Agent** patched `GHSA-QRWJ-VH9X-GW5V`, a cross-agent SSRF flaw that let an authenticated attacker controlling one workspace agent abuse HTTP `307`/`308` redirects to replay privileged requests to another agent, enabling cross-tenant file access, file writes, and command execution; fixes were released in versions `v2.34.4`, `v2.33.10`, `v2.32.9`, and `v2.29.19 ESR`. **Coolify** disclosed a critical authenticated command injection issue tied to unsafe handling of deployment fields such as `dockerfile_location`, allowing RCE and secrets exposure through deployment logs, while **OpenRemote** fixed `GHSA-cgfv-jrfp-2r7v`, an authenticated SQL injection bug in datapoint crosstab export that could expose other tenants’ data, Keycloak configuration, and encrypted credentials. Additional disclosures affected AI and package-management components. **Langroid** fixed a prompt-injection-driven flaw in `Neo4jChatAgent` that executed LLM-generated Cypher without validation, allowing unauthorized graph operations and possible OS-level impact when dangerous Neo4j procedures were enabled; the issue was resolved in version `0.65.5` with new safety controls that were also extended to `ArangoChatAgent`. **pnpm** also reported a path traversal weakness in `configDependencies` processing from `pnpm-lock.yaml`, where a malicious repository could force symlink creation outside `node_modules/.pnpm-config` even with `--ignore-scripts`, creating a filesystem write primitive within or potentially beyond the project directory.
Jul 10, 2026