Arbitrary JavaScript execution via unsafe bytes defaults
Published May 13, 2026 · Updated Aug 28, 2026
Code injection in protobuf.js before 7.5.6 and 8.0.0 through 8.0.1 allows attackers to execute arbitrary JavaScript. Generated toObject code embeds a non-string bytes-field default as an unsafe expression instead of safely encoding it as data. Exploitation requires an application to load an attacker-controlled descriptor and call toObject with defaults enabled; trusted schemas are not directly affected.
Summary
What happened
Code injection in protobuf.js before 7.5.6 and 8.0.0 through 8.0.1 allows attackers to execute arbitrary JavaScript. Generated toObject code embeds a non-string bytes-field default as an unsafe expression instead of safely encoding it as data. Exploitation requires an application to load an attacker-controlled descriptor and call toObject with defaults enabled; trusted schemas are not directly affected.
The record
- CVE
- CVE-2026-44293
- Published
- May 13, 2026
- Updated
- Aug 28, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat OpenShift AI
- Classifications
- CWE-94
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo