BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-5758High confidence

Mafintosh's protocol-buffers-schema is vulnerable to prototype pollution

Mafintosh · Protocol-buffers-schema parser

6.5MediumCVSS 3.1
Recommended action
Within 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:High, raised one band.upgradedsince 15 Apr 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.69% for the current model date.

Compensating controls

  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Mafintosh Protocol-buffers-schema parser and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmprotocol-buffers-schema< 3.6.13.6.1GitHub advisory ↗github reviewed aggregator · 16 Apr 2026
npmprotocol-buffers-schemaSEMVER: introduced 0; fixed 3.6.13.6.1OSV record ↗aggregator derived · 10 Sep 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-22993

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
01

What, why and how

JavaScript is vulnerable to prototype pollution in Mafintosh's protocol-buffers-schema Version 3.6.0, where an attacker may alter the application logic, bypass security checks, cause a DoS or achieve remote code execution.

What

JavaScript is vulnerable to prototype pollution in Mafintosh's protocol-buffers-schema Version 3.6.0, where an attacker may alter the application logic, bypass security checks, cause a DoS or achieve remote code execution.

Why

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

What

JavaScript is vulnerable to prototype pollution in Mafintosh's protocol-buffers-schema Version 3.6.0, where an attacker may alter the application logic, bypass security checks, cause a DoS or achieve remote code execution.

Why

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.

Likely attack path
a network path → Exposure of Sensitive Information to an Unauthorized Actor → execute code or commands in the affected security context
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-200 ↗

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.INoneIntegrity impact: No direct loss is represented by this metric.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkUnauthenticatedRemote code executionCWE-200Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20260422Security Bulletin 22 April 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 April 2026, published on 22 April 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1256Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2026-54515 Référence CVE CVE-2026-54516 https://www.cve.org/CVERecord?id=CVE-2026-54516 Référence CVE CVE-2026-54517 https://www.cve.org/CVERecord?id=CVE-2026-54517 Référence CVE CVE-2026-54518 https://www.cve.org/CVERecord?id=CVE-2026-54518 Référence CVE CVE-2026-54874 https://www.cve.org/CVERecord?id=CVE-2026-54874 Référence CVE CVE-2026-5588 https://www.cve.org/CVERecord?id=CVE-2026-5588 Référence CVE CVE-2026-5598 https://www.cve.org/CVERecord?id=CVE-2026-5598 Référence CVE CVE-2026-55995 https://www.cve.org/CVERecord?id=CVE-2026-55995 Référence CVE CVE-2026-56130 https://www.cve.org/CVERecord?id=CVE-2026-56130 Référence CVE CVE-2026-5758 https://www.cve.org/CVERecord?id=CVE-2026-5758 Référence CVE CVE-2026-58010 https://www.cve.org/CVERecord?id=CVE-2026-58010 Référence CVE CVE-2026-58011 https://www.cve.org/CVERecord?id=CVE-2026-58011 Référence CVE CVE-2026-58012 https://www.cve.org/CVERecord?id=CVE-2026-58012 Référence CVE CVE-2026-58013 https://www.cve.org/CVERecord?id=CVE-2026-58013 Référence CVE CVE-2026-58014 https://www.cve.org/CVERecord?id=CVE-2026-58014 Référence CVE CVE-2026-58015 https://www.cve.org/CVERecord?id=CVE-2026-58015 Référence CVE CVE-2026-58055 https://www.cve.org/CVERecord?id=CVE-2026-58055 Référence CVE CVE-2026-58059 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0958Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2026-54900 Référence CVE CVE-2026-54901 https://www.cve.org/CVERecord?id=CVE-2026-54901 Référence CVE CVE-2026-54902 https://www.cve.org/CVERecord?id=CVE-2026-54902 Référence CVE CVE-2026-54903 https://www.cve.org/CVERecord?id=CVE-2026-54903 Référence CVE CVE-2026-54904 https://www.cve.org/CVERecord?id=CVE-2026-54904 Référence CVE CVE-2026-54905 https://www.cve.org/CVERecord?id=CVE-2026-54905 Référence CVE CVE-2026-54906 https://www.cve.org/CVERecord?id=CVE-2026-54906 Référence CVE CVE-2026-5588 https://www.cve.org/CVERecord?id=CVE-2026-5588 Référence CVE CVE-2026-5598 https://www.cve.org/CVERecord?id=CVE-2026-5598 Référence CVE CVE-2026-5758 https://www.cve.org/CVERecord?id=CVE-2026-5758 Référence CVE CVE-2026-5795 https://www.cve.org/CVERecord?id=CVE-2026-5795 Référence CVE CVE-2026-59869 https://www.cve.org/CVERecord?id=CVE-2026-59869 Référence CVE CVE-2026-59871 https://www.cve.org/CVERecord?id=CVE-2026-59871 Référence CVE CVE-2026-59873 https://www.cve.org/CVERecord?id=CVE-2026-59873 Référence CVE CVE-2026-59874 https://www.cve.org/CVERecord?id=CVE-2026-59874 Référence CVE CVE-2026-59875 https://www.cve.org/CVERecord?id=CVE-2026-59875 Référence CVE CVE-2026-6009 https://www.cve.org/CVERecord?id=CVE-2026-6009 Référence CVE CVE-2026-6100 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0788Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2026-44290 Référence CVE CVE-2026-44291 https://www.cve.org/CVERecord?id=CVE-2026-44291 Référence CVE CVE-2026-44292 https://www.cve.org/CVERecord?id=CVE-2026-44292 Référence CVE CVE-2026-44293 https://www.cve.org/CVERecord?id=CVE-2026-44293 Référence CVE CVE-2026-44294 https://www.cve.org/CVERecord?id=CVE-2026-44294 Référence CVE CVE-2026-45740 https://www.cve.org/CVERecord?id=CVE-2026-45740 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=CVE-2026-46300 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Référence CVE CVE-2026-5598 https://www.cve.org/CVERecord?id=CVE-2026-5598 Référence CVE CVE-2026-5758 https://www.cve.org/CVERecord?id=CVE-2026-5758 Référence CVE CVE-2026-6472 https://www.cve.org/CVERecord?id=CVE-2026-6472 Référence CVE CVE-2026-6473 https://www.cve.org/CVERecord?id=CVE-2026-6473 Référence CVE CVE-2026-6474 https://www.cve.org/CVERecord?id=CVE-2026-6474 Référence CVE CVE-2026-6475 https://www.cve.org/CVERecord?id=CVE-2026-6475 Référence CVE CVE-2026-6477 https://www.cve.org/CVERecord?id=CVE-2026-6477 Référence CVE CVE-2026-6478 https://www.cve.org/CVERecord?id=CVE-2026-6478 Référence CVE CVE-2026-6479 https://www.cve.org/CVERecord?id=CVE-2026-6479 Référence CVE CVE-2026-6637 https://www.cve.org/CVERecord?id=CVE-2026-6637 Ré

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
Protocol-buffers-schema parser: 3.6.0 < 3.6.1
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 15 Apr 2026 · Last source change 15 Apr 2026, 18:55 UTC · CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-22993
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD awaiting enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-5758 · cve.blacktree.nl