Loading story…
OpenZeppelin disclosed a code-injection vulnerability in @openzeppelin/wizard that affected versions through 0.10.8, allowing attacker-controlled values in opts.name and opts.uri to be written into generated Hardhat and Foundry example test files without proper escaping. By breaking out of a string literal, a malicious input could inject arbitrary code into the generated project, which would then run when a developer executed test workflows such as npm test or forge test.
The company said the issue was fixed in @openzeppelin/wizard 0.10.9, which now escapes opts.name and opts.uri during test-file generation. OpenZeppelin also said the hosted Contracts Wizard at wizard.openzeppelin.com had already been redeployed with the fix, and that the documented public API was not affected because the vulnerable zipHardhat and zipFoundry functions were not part of the documented public exports; users invoking those functions with externally controlled strings were advised to upgrade.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
On 2026-05-20, OpenZeppelin published a security advisory for @openzeppelin/wizard versions up to and including 0.10.8 describing code injection in generated Hardhat and Foundry tests via unsanitized opts.name and opts.uri. The advisory recommended upgrading to version 0.10.9 and noted that documented public API users were not affected.
On 2026-05-20, OpenZeppelin released @openzeppelin/wizard version 0.10.9 to address GHSA-4x76-22x2-rx8v. The fix escapes opts.name and opts.uri when generating Hardhat and Foundry test files, and the release notes said the issue affected callers of zipHardhat and zipFoundry.
OpenZeppelin said the hosted Contracts Wizard at wizard.openzeppelin.com had already been redeployed with a fix for a code injection flaw involving unsanitized opts.name and opts.uri in generated Hardhat and Foundry test files. The issue could allow attacker-controlled input to be inserted into generated test code and execute when developers ran tests.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
github.com
Open sourcegithub.com
Open sourceMap 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.
A critical software supply-chain vulnerability, **CVE-2026-23947** (CVSS **9.3**), was disclosed in *Orval*, a widely used npm tool that generates type-safe TypeScript/JavaScript clients from OpenAPI/Swagger specifications. The flaw allows **code injection** when Orval processes untrusted or compromised API specifications: attacker-controlled content in the `x-enumDescriptions` / `x-enum-descriptions` field is embedded without proper escaping in `getEnumImplementation()`, enabling malicious TypeScript/JavaScript to be written into generated client/schema files during `const enum` generation. Successful exploitation can lead to **arbitrary code execution in environments consuming the generated clients**, shifting risk to downstream developers and build/runtime pipelines that treat generated code as trusted. Affected versions are reported as **7.10.0 through 8.0.2**, and vendor guidance indicates updating to a fixed release (noted as *Orval* **8.0.2**) to remediate; the issue is described as similar to **CVE-2026-22785** but impacting a different `@orval/core` code path not covered by the earlier fix.
Jun 29, 2026
Open WebUI disclosed and patched a high-severity broken access control vulnerability in its Tool Valves feature, tracked as **CVE-2026-34222** and **GHSA-7429-hxcv-268m**. The flaw affects versions earlier than `v0.8.11` and allowed a low-privileged Member user with a valid authorization token to access sensitive valve configuration data that should have been restricted. According to the disclosure, the vulnerable endpoint did not properly enforce authorization checks, exposing secrets such as API keys used by backend integrations. SEC Consult reported that exploitation required knowledge of a Tool ID, but said those identifiers were easy to derive because they are based on tool names and imported tools use predictable values. The issue was validated against Open WebUI `v0.7.2`, and the project confirmed a fix in `v0.8.11`, with remediation verified on the development branch before coordinated disclosure. Organizations running affected releases should treat Tool Valve secrets as potentially exposed and upgrade to a patched version.
Jun 29, 2026
Two high-severity flaws were disclosed in widely used JavaScript libraries, exposing applications to sandbox bypass and arbitrary code execution. **CVE-2026-34208** affects SandboxJS before `0.8.36` and allows attacker-supplied code to evade protections on direct assignment to global objects by abusing an exposed constructor path. The bypass uses `this.constructor.call(target, attackerObject)` to reach the internal `SandboxGlobal` function while `Function.prototype.call` remains permitted, enabling arbitrary properties to be written into host global objects and persist across sandbox instances in the same process. A separate issue, **CVE-2026-41242**, impacts `protobufjs` before `8.0.1` and `7.5.5`, where attackers can inject arbitrary code into Protocol Buffers definition `type` fields and trigger execution during object decoding with a malicious schema. The flaw is tracked as **CWE-94** and carries a CVSS v4 rating reflecting network-reachable exploitation with high impact to confidentiality, integrity, availability, and downstream systems. Maintainers released fixes in SandboxJS `0.8.36` and protobufjs `8.0.1` and `7.5.5`.
Jun 29, 2026