Skip to main content
VulnerabilityPublished Updated

CVE-2026-63630: alam00000 bentopdf · Deserialization of Untrusted Data

Affects alam00000 bentopdfSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.4 Low : upgrade to 2.8.7 when convenient.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 3.1 base score
3.4Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.8.7
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Upgrade bentopdf and alam00000/bentopdf to 2.8.7.

Affected software

ProductAffectedFixed in
alam00000bentopdfAffected
  • <2.8.7
Fixed in
  • 2.8.7
GitHubalam00000/bentopdfpkg:github/alam00000/bentopdfOther threatsAffected
  • <2.8.7
Fixed in
  • 2.8.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in BentoPDF version 2.8.7. Users should upgrade to version 2.8.7 or later to remediate this issue. No additional mitigation is required if the upgrade is applied.

Description

BentoPDF is a client-side PDF toolkit that is self hostable. In 2.8.6 and earlier, deserializeWorkflow() accepts the Timestamp node's tsaUrl control from imported JSON without schema or destination validation. When a user imports the crafted workflow and runs it against a PDF, timestampPdf() sends an RFC 3161 TimeStampReq containing the PDF's SHA-256 MessageImprint to the attacker-selected endpoint. The default self-hosted configuration does not set VITE_CORS_PROXY_URL, so the request bypasses the proxy's ALLOWED_TSA_HOSTS checks and is sent directly. The disclosed digest can confirm that a document matches a known file and can correlate the same document across users without revealing its contents. This vulnerability is fixed in 2.8.7.

References

Community reviews

Loading reviews…