Blog · 2-hour update · 2026-10-24

CVE-2026-94075 Tribulant Software Newsletters newsletters-lite: critical remote flaw, how to fix

On 24 October 2026, 16 new CVEs were published that we track: 4 critical, 0 already exploited in the wild (CISA KEV) and 0 with a fix or vendor patch available. Each one is ranked by severity, exploitation signals and how easy it is to reach, so you can patch the right ones first.

What happened in this 2-hour window: the most serious item is CVE-2026-94075 (critical, CVSS 9.8, priority 39/100). Recommended action: apply the vendor mitigation. 5 of the 8 top items can be attacked remotely without a login. 0 of 16 new CVEs already have a fix or vendor patch; for the other 16, follow the downgrade or mitigation steps until one ships.

Patch these first

CVE-2026-94075: Deserialization of Untrusted Data vulnerability in Tribulant Software Newsletters newsletters-lite allows Obje

Critical severity (CVSS 9.8), priority 39/100 (patch this month). Signals: critical severity; remotely exploitable, no login, no user action. Recommended action: apply the vendor mitigation.

References: NVD

CVE-2026-114196: Deserialization of Untrusted Data vulnerability in paytiumsupport Paytium paytium allows Object Injection.This

Critical severity (CVSS 9.8), priority 39/100 (patch this month). Signals: critical severity; remotely exploitable, no login, no user action. Recommended action: apply the vendor mitigation.

References: NVD

CVE-2026-112866: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in WPFactor

Critical severity (CVSS 9.3), priority 38/100 (patch this month). Signals: critical severity; remotely exploitable, no login, no user action. Recommended action: apply the vendor mitigation.

References: NVD

CVE-2026-111402: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Tribulan

Critical severity (CVSS 9.3), priority 38/100 (patch this month). Signals: critical severity; remotely exploitable, no login, no user action. Recommended action: apply the vendor mitigation.

References: NVD

CVE-2026-114190: Insertion of Sensitive Information Into Sent Data vulnerability in Hai Zheng / Lite Speed Cache LiteSpeed Cach

Medium severity (CVSS 5.9), priority 26/100 (routine). Signals: remotely exploitable, no login, no user action. Recommended action: apply the vendor mitigation.

References: NVD

CVE-2026-115975: Broken access control in JiraController in Cervantes version v1.3-beta could allow an attacker to create, edit

High severity (CVSS 7.1), priority 25/100 (routine). Signals: high severity. Recommended action: apply the vendor mitigation.

References: NVD

CVE-2026-114697: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in QuarkA Q

High severity (CVSS 7.1), priority 25/100 (routine). Signals: high severity. Recommended action: apply the vendor mitigation.

References: NVD

CVE-2026-114695: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Infomani

High severity (CVSS 7.1), priority 25/100 (routine). Signals: high severity. Recommended action: apply the vendor mitigation.

References: NVD

How to act on this list

1. Start with anything marked exploited or patch now.
2. Check what you run: see how to check a version and patch it on Linux, Windows, pip and npm.
3. Prefer the vendor or distro fix. If none exists, read when to downgrade and when to mitigate.
4. Verify afterwards. Distros often fix a flaw without changing the upstream version, here is how to confirm.

FAQ

What is the most serious vulnerability published on 24 October 2026?

CVE-2026-94075 (Deserialization of Untrusted Data vulnerability in Tribulant Software Newsletters newsletters-lite allows Obje) ranks highest, with a priority score of 39/100. Recommended action: apply the vendor mitigation.

Are any of the new CVEs exploited in the wild?

None of the new CVEs were on the CISA Known Exploited Vulnerabilities list when this was written. Keep watching the list, it changes daily.

Should I downgrade if there is no fix yet?

Only when an older release is confirmed unaffected and the package is not a core system component. Downgrades can break dependent software, so test first and hold the package until a fix ships.

Sources

• NIST National Vulnerability Database: CVE details and affected versions
• CVE Program: official CVE records
• CISA Known Exploited Vulnerabilities catalog: exploitation in the wild
• FIRST EPSS: exploit probability
• Distribution and vendor advisories linked under each item.

← All posts