rootpwn

high · CVSS v3 8.8 · EPSS 0.00129

CVE-2026-91813

Foxit PDF Editor/Reader’s update mechanism contains a race condition that allows a local attacker to replace an update package between downl

Overview

Foxit PDF Editor/Reader’s update mechanism contains a race condition that allows a local attacker to replace an update package between download and extraction, enabling arbitrary code execution with elevated privileges. The flaw can be exploited on systems where Foxit is installed and updates are performed automatically.

Description

A vulnerability in Foxit PDF Editor/Reader’s update mechanism allows an update package to be replaced between download and high-privilege extraction due to insufficient file locking and integrity validation. This could enable local attackers to execute arbitrary code with elevated privileges.

Impact

Confidentiality, Integrity, and Availability are at risk: a local user with administrative privileges can gain full control of the affected system. Defenders should be aware that any user who can trigger an update may compromise the machine.

Remediation

Apply the vendor-supplied patch that enforces file locking and verifies the integrity of the update package before extraction. Disable automatic updates or configure the update client to use signed packages only. Monitor for anomalous update activity and restrict write permissions to the update directory.

Risk context

Severity is high (CVSS 8.8) but EPSS is low (0.00129), indicating a low probability of exploitation in the wild. Nonetheless, the high impact warrants prompt patching.

Affected products

  • Foxit PDF Editor
  • Foxit PDF Reader

Scores

Severity
high
CVSS v2
6.8
CVSS v3
8.8
CVSS v4
—
EPSS
0.00129

foxit pdf update local-privilege race-condition high-severity

← All CVEs

Related CVEs

high

CVE-2026-88997

The JSM Show Post Metadata WordPress plugin before 4.9.1 does not properly escape a post meta key before outputting it into an inline event-handler attribute in an admin-facing meta box, allowing users with contributor-level access and above to inject arbitrary JavaScript that executes in the session of a higher-privileged user who reviews the affected post.

View analysis

high

CVE-2026-89425

UTF8DataInputJsonParser._reportInvalidToken() in FasterXML jackson-core builds the offending-token text for its error message by appending Java identifier characters to a StringBuilder in a loop that has no upper bound. Unlike the three sibling parser implementations, including UTF8StreamJsonParser, it never consults ErrorReportConfiguration.getMaxErrorTokenLength() (default 256). A malformed token supplied to a parser created through JsonFactory.createParser(DataInput) is therefore accumulated in full. No StreamReadConstraints setting mitigates this: maxDocumentLength cannot be applied to DataInput sources at all, and maxStringLength does not cover this path because the accumulation bypasses ReadConstrainedTextBuffer. The reporter measured a 20,000,109-character exception message from a 20-million-character malformed token on the DataInput path, against 367 characters for identical input on the InputStream path. Scaling the payload drives the StringBuilder, which also incurs byte-to-char expansion and internal array doubling, to many times the raw payload size and can trigger OutOfMemoryError for the whole JVM. UTF8DataInputJsonParser was introduced in 2.8.0 together with createParser(DataInput); releases before 2.8.0 do not contain the affected class.

View analysis

high

CVE-2026-91073

The Subscribe Forms WordPress plugin before 1.6.3 does not sanitise and escape one of its form settings before outputting it in a page, allowing authenticated users with the Author role and above to perform Stored Cross-Site Scripting attacks that execute in the browser of any visitor who views a page embedding the form, including logged-out visitors and administrators.

View analysis

high

CVE-2026-91776

TypeDeserializerBase._findDeserializer() in FasterXML jackson-databind caches the resolved deserializer under the raw, attacker-supplied type ID. When name-based polymorphism is configured with a fallback, for example @JsonTypeInfo(use = Id.NAME, defaultImpl = ...), every distinct unrecognized type ID resolves to the same fallback deserializer but is retained as its own key in the _deserializers map. That map has no configurable bound and lives for the lifetime of the type deserializer, so an attacker who can repeatedly supply fresh unknown type IDs causes monotonic memory retention across requests. The reporter observed 10,000 retained entries from 10,000 distinct unknown IDs, against a single entry for a control that repeated one unknown ID the same number of times, isolating attacker-controlled key cardinality from request volume. Exploitation requires an application that enables name-based polymorphism with a defaultImpl or equivalent fallback, accepts attacker-influenced type IDs, and reuses a long-lived ObjectMapper across requests. The fix stops caching fallback resolutions for unrecognized IDs and bounds both the number of cached entries and the length of a cacheable type ID.

View analysis