Is there a public exploit for CVE-2026-41242?

Yes. Proof-of-concept code for CVE-2026-41242 has been published publicly.

Is there a proof of concept for CVE-2026-41242?

Yes — 2 proof-of-concept entries are linked on this page, from public repositories and community submissions. They are listed for authorised testing only.

How severe is CVE-2026-41242?

CVE-2026-41242 scores CVSS 9.4 (v4.0), rated critical. EPSS puts the chance of exploitation in the next 30 days at 0.77%.

What does CVE-2026-41242 affect?

CVE-2026-41242 affects protobufjs protobuf.js.

9.4 Critical

protobufjs compiles protobuf definitions into JavaScript (JS) functions.

CVE-2026-41242

protobufjs compiles protobuf definitions into JavaScript (JS) functions. In versions prior to 8.0.1, 7.5.5, and 6.11.6, attackers can inject arbitrary code in the "type" fields of protobuf definitions, which will then execute during object decoding using that definition. Versions 8.0.1, 7.5.5, and 6.11.6 patch the issue.

Proof-of-concept code is published

Public PoC

Public PoC4chech/CVE-2026-41242
Public PoCGiangdurian/CVE-2026-41242

Signals come from Exploit-DB, Metasploit, Nuclei and published proof-of-concept repositories. Their absence means nothing was found, not that nothing exists.

Assessment

CVSS: 9.4 (v4.0)
Severity: Critical
EPSS: 0.77% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Public PoC
Published: 18 April 2026
Last updated: 3 November 2026
Affected: protobufjs · protobuf.js
Assigner: GitHub_M

CVSS vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

At the source

EUVD (ENISA)

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 9 + 5? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-41242