PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-82865 pdfme CVE debrief

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-31T09:17:07.110Z and has not been modified since then. The vulnerability affects pdfme schemas before version 5.5.10 and involves a cross-site scripting issue in the multiVariableText property panel. This vulnerability allows attackers to inject arbitrary JavaScript when users open the Designer and select a multiVariableText field without variable placeholders. Developers and administrators using pdfme schemas should review and implement vendor remediation guidance to prevent potential exploitation. The evidence for this CVE is limited, so verification through primary official records and vendor remediation guidance is necessary.

Vendor
pdfme
Product
schemas
CVSS
LOW 2.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-31
Original CVE updated
2026-08-31
Advisory published
2026-08-31
Advisory updated
2026-08-31

Who should care

Developers and administrators using pdfme schemas; review and implement vendor remediation guidance to prevent potential exploitation. Affected operators, platforms, vulnerability-management, and security teams should be aware of the vulnerability and its potential impact. They should review compensating controls for exposed systems while remediation is scheduled and verified.

Technical summary

pdfme schemas before 5.5.10 contains a cross-site scripting vulnerability in the multiVariableText property panel; attackers can inject arbitrary JavaScript when users open the Designer and select a multiVariableText field without variable placeholders. The vulnerability is triggered by unsanitized i18n label values assigned to innerHTML. This issue can be mitigated by reviewing and implementing vendor remediation guidance, verifying affected versions, and assessing user interaction requirements.

Defensive priority

Low-priority defensive review recommended due to limited attack surface; verify affected versions and assess user interaction requirements.

Recommended defensive actions

  • Verify affected versions of pdfme schemas and assess user interaction requirements
  • Review and implement vendor remediation guidance
  • Monitor for potential exploitation attempts
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The evidence for this CVE is limited; verify vulnerability details through primary official records and vendor remediation guidance. Affected product deployments should be confirmed to exist in managed environments, and an owner should be assigned for follow-up. The CVE record was published on 2026-08-31T09:17:07.110Z and has not been modified since then. Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-82865 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-82865

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-82865 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-82865

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.