Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-jjwr-xmw6-gf78

Apache PDFBox has Path Traversal through PDComplexFileSpecification.getFilename() function

CVSS 5.3 MediumEPSS 0.0099 · 62nd percentile

Published by the GitHub Advisory Database at 10 Mar 2026, 18:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.pdfbox:pdfbox-examplesMaven>=2.0.24, <3.0.73.0.7
Identifiers
GHSA-jjwr-xmw6-gf78 · CVE-2026-23907
Weakness (CWE)
CWE-22
Tags
Published
10 Mar 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache PDFBox's pdfbox-examples package, versions 2.0.24 through 2.0.35 and 3.0.0 through 3.0.6, has a path traversal flaw in its ExtractEmbeddedFiles example. The example appends the embedded file name taken from the PDF to the extraction path without checking it. An attacker who supplies a crafted PDF could cause files to be written outside the intended directory when the example is run. Upgrade to version 3.0.7. Users who copied this example into their own code should review that code and confirm the extraction path is restricted to the intended directory.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0099, the 62nd percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.