ETK-2026-1284Zero's internal tracking ID, independent of the CVE number.

waiting for further signalsZero needs more public information before it can validate it.

GHSA-ppm7-rg95-2c2p ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
go:github.com/pdfcpu/pdfcpu >= 0.8.0, < 0.16.2
fixed in 0.16.2
CWE-311 Missing Encryption of Sensitive Data
ETK-2026-1284Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:golang/github.com/pdfcpu/pdfcpu
cvss7.0ethiack provisional
9d 01h 56msince last run
22mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dwaiting for further signals+0.2d
0
+2d
+4d
+6d
+8d
+10d

description

pdfcpu versions before 0.16.2 can leave strings from compressed objects readable in PDFs that appear encrypted. An attacker able to obtain such an output file may read exposed content without the PDF password when the input contains object streams.

mitigation

Upgrade pdfcpu to version 0.16.2 or later. Review PDFs encrypted with affected versions for sensitive plaintext and regenerate them from trusted source files after upgrading.

fixed in 0.16.2

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
22m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-11 22:52Z

this entry in the feed

GET /api/v1/feed/ETK-2026-1284

{
  "etk_id": "ETK-2026-1284",
  "cve_id": null,
  "display_id": "ETK-2026-1284",
  "ghsa_id": "GHSA-ppm7-rg95-2c2p",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Plaintext disclosure during PDF encryption in pdfcpu",
  "summary": "pdfcpu versions before 0.16.2 can leave strings from compressed objects readable in PDFs that appear encrypted. An attacker able to obtain such an output file may read exposed content without the PDF password when the input contains object streams.",
  "mitigation": "Upgrade pdfcpu to version 0.16.2 or later. Review PDFs encrypted with affected versions for sensitive plaintext and regenerate them from trusted source files after upgrading.",
  "vendor": "go",
  "product": "go:github.com/pdfcpu/pdfcpu",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.8.0, < 0.16.2"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "0.16.2"
      ],
      "package_name": "github.com/pdfcpu/pdfcpu",
      "purl": "pkg:golang/github.com/pdfcpu/pdfcpu"
    }
  ],
  "cwes": [
    311
  ],
  "cvss_score": 7,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 22.09673345,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-11T22:52:29+00:00",
      "days": -9.249273120532408,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T04:51:26.219671+00:00",
      "url": "https://github.com/pdfcpu/pdfcpu/security/advisories/GHSA-ppm7-rg95-2c2p"
    }
  }
}

published 2026-10-12 02:33Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.