Home
» Security vulnerabilities
» CVE-2026-5940
Calling a function that triggers a UI refresh after removing comments via a script may access an invalidated object, leading to program crashes.
Published: 2026-04-27
Last update: 2026-04-29
Assigner:
14984358-7092-470d-8f34-ade47a7658a2
Source: 14984358-7092-470d-8f34-ade47a7658a2
NVD Status: Analyzed ,CVE State: published
Threat Intelligence & Risk Assessment for CVE-2026-5940
Conclusion & alert: CVE-2026-5940 is rated Low Risk (32/100) : CVSS High severity, with low exploitation likelihood (EPSS 0.01%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Exploit prediction scoring system (EPSS) score for CVE-2026-5940
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2026-04-27
—
0.01%
—
Full EPSS history
(1 record total)
Common vulnerability scoring system (CVSS) metrics for CVE-2026-5940
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
7.8
3.1
HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8
5.9
14984358-7092-470d-8f34-ade47a7658a2
5.5
3.1
MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8
3.6
[email protected]
Weakness enumeration for CVE-2026-5940
GitHub Security Advisory for CVE-2026-5940
GHSA-gmwv-jpmc-ppqc · Severity: high
— Calling a function that triggers a UI refresh after removing comments via a script may access an...
Affected software / configurations for CVE-2026-5940
Vendor
Product
Version
Raw CPE
foxit
pdf_editor
< 13.2.4
cpe:2.3:a:foxit:pdf_editor:*:*:*:*:*:*:*:*
foxit
pdf_editor
>= 14.0.0, < 14.0.4
cpe:2.3:a:foxit:pdf_editor:*:*:*:*:*:*:*:*
foxit
pdf_editor
>= 2023.0.0, < 2026.1.1
cpe:2.3:a:foxit:pdf_editor:*:*:*:*:*:*:*:*
foxit
pdf_reader
< 2026.1.1
cpe:2.3:a:foxit:pdf_reader:*:*:*:*:*:*:*:*
References for CVE-2026-5940
cvelogic
Threat Intelligence