# CVE-2026-119743: pdfmake < 0.3.14 Shared Cache Access Policy Bypass


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-cw47-gww7-39hm

## What is CVE-2026-119743?

CVE-2026-119743 is a medium-severity vulnerability in bpampuch pdfmake, published on 9 Nov 2026. 

### Official description

pdfmake before 0.3.14 contains a shared resource caching vulnerability that allows attackers to access cross-document cached resources by exploiting a process-wide virtual file system keyed only by URL without request headers or per-document access enforcement. Attackers can retrieve resources fetched with another caller's credentials or from URLs that a later document's access policy would deny, resulting in cross-document information disclosure and bypass of the URL access policy.

Weakness: CWE-524 (Use of Cache Containing Sensitive Information)

## Which versions are affected by CVE-2026-119743?


## How do I fix CVE-2026-119743?

No fix has been published for CVE-2026-119743 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119743 being exploited?

There is no known exploitation of CVE-2026-119743 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119743 and fix it if it is affected.

What it is: CVE-2026-119743 is a medium-severity vulnerability in bpampuch pdfmake, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-119743 in the wild and no public exploit code.

Affected product: bpampuch pdfmake. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119743/ (Markdown: https://insights.sbomify.com/CVE-2026-119743/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119743
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119743
- OSV: https://osv.dev/vulnerability/CVE-2026-119743

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119743/
Summaries are generated and may contain mistakes; the official description above is the record.