How many CVEs have patched finish_pdb_parse?

1 published CVEs changed finish_pdb_parse in radareorg/radare2, in 1 distinct patches totalling 3 changed lines, between 2026 and 2026.

What is the latest CVE that changed finish_pdb_parse?

CVE-2026-40499 (radare2 < 6.1.4 Command Injection via PDB Parser print_gvars()), published 2026-04-15, changed lines 636 of libr/bin/format/pdb/pdb.c.

How does finish_pdb_parse compare to the rest of radareorg/radare2?

radareorg/radare2 has 101 CVEs with a located fix in total; 1 of them changed finish_pdb_parse.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

radareorg/radare2

Function

finish_pdb_parse

Name: finish_pdb_parse in radareorg/radare2: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

libr/bin/format/pdb/pdb.c

Last patched April 15, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

3

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

finish_pdb_parse in radareorg/radare2 was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 3 lines in total.

radareorg/radare2 has 101 CVEs with a located fix in total, so 1% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed finish_pdb_parse, newest first, with the lines each fix touched.

radare2 < 6.1.4 Command Injection via PDB Parser print_gvars()
CVE-2026-40499 · line 636 · +0 −3
High · CVSS 8.4
EPSS 1.7%2026-04-15

Get an alert when the next CVE fix lands in radareorg/radare2, with the patched functions.

Monitor radare2 CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in radareorg/radare2 changed by the most CVE fixes.

r_bin_ne_get_relocs4 CVEs · libr/bin/format/ne/ne.c r_bin_ne_get_entrypoints4 CVEs · libr/bin/format/ne/ne.c parse_die3 CVEs · libr/bin/dwarf.c r_bin_ne_get_segments3 CVEs · libr/bin/format/ne/ne.c __get_target_os3 CVEs · libr/bin/format/ne/ne.c r_coresym_cache_element_new3 CVEs · libr/bin/format/mach0/coresymbolication.c

All patched functions in radareorg/radare2

Frequently asked questions

Common questions about CVE fixes to finish_pdb_parse.

How many CVEs have patched finish_pdb_parse?: 1 published CVEs changed finish_pdb_parse in radareorg/radare2, in 1 distinct patches totalling 3 changed lines, between 2026 and 2026.
What is the latest CVE that changed finish_pdb_parse?: CVE-2026-40499 (radare2 < 6.1.4 Command Injection via PDB Parser print_gvars()), published 2026-04-15, changed lines 636 of libr/bin/format/pdb/pdb.c.
How does finish_pdb_parse compare to the rest of radareorg/radare2?: radareorg/radare2 has 101 CVEs with a located fix in total; 1 of them changed finish_pdb_parse.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track radareorg/radare2 CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing