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

No public exploit for CVE-2026-20518 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

How severe is CVE-2026-20518?

CVE-2026-20518 scores CVSS 4.2 (v3.1), rated medium. EPSS puts the chance of exploitation in the next 30 days at 0.16%.

What does CVE-2026-20518 affect?

CVE-2026-20518 affects MediaTek, Inc. MediaTek chipset.

4.2 Medium

In geniezone, there is a possible information disclosure due to a missing bounds check.

CVE-2026-20518

In geniezone, there is a possible information disclosure due to a missing bounds check. This could lead to local information disclosure if a malicious actor has already obtained the System privilege. User interaction is needed for exploitation. Patch ID: ALPS10867524 / ALPS10876355; Issue ID: MSV-6674.

Assessment

CVSS: 4.2 (v3.1)
Severity: Medium
EPSS: 0.16% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 7 September 2026
Last updated: 2 November 2026
Affected: MediaTek, Inc. · MediaTek chipset
Assigner: MediaTek

CVSS vectorCVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N

At the source

EUVD (ENISA)

References

https://www.mediatek.com/product-security-bulletin/September-2026

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 4 + 6? *

Query this programmatically

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

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