CVE-2019-12958

What it is

In Xpdf 4.01.01, a heap-based buffer over-read could be triggered in FoFiType1C::convertToType0 in fofi/FoFiType1C.cc when it is trying to access the second privateDicts array element, because the privateDicts array has only one element allocated.

At a glance

Exploitability

Can be exploited locally on the machine without logging in, but needs a user to act. High risk of service disruption.

Exploit odds

1.2% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2019-06-25 00:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 02:15 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.2% in the next 30 days (EPSS).
• Severity: 5.5 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2019-06-25 00:15 UTC

Last modified

2026-06-17 02:15 UTC

Exploit probability

1.2% · EPSS, next 30 days

Weakness

CWE-125 · Out-of-bounds read

Record status

Modified

Affected

• Glyphandcog Xpdfreader 4.01.01

Attack profile CVSS 3.0 · 5.5

Attack vector

Local

Complexity

Low

Privileges needed

None

User interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2019-12958.md and follow it. Check whether this project is affected by CVE-2019-12958. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge