PatchTheCVEBlog · 2-hour update · 2026-10-28
CVE-2026-110879 jackson-databind validates: critical remote flaw, how to fix
By the PatchTheCVE security team · Updated 2026-10-28 · Data from NVD, CISA KEV, EPSS and vendor advisories
Critical severity (CVSS 9.8), remotely exploitable, no login needed. Recommended action: apply the vendor mitigation.
On 28 October 2026, 7 new CVEs were published that we track: 2 critical, 0 already exploited in the wild (CISA KEV) and 1 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.
Key takeaways
- Most urgent: CVE-2026-110879 (jackson-databind validates): apply the vendor mitigation.
- 4 of the top 7 can be attacked over the network without a login.
- 1 of 7 new CVEs already have a fix or vendor patch.
- Most affected vendors: a2ui-project, artbees.
What happened in this 2-hour window: the most serious item is CVE-2026-110879 (critical, CVSS 9.8, priority 39/100). Recommended action: apply the vendor mitigation. 4 of the 7 top items can be attacked remotely without a login. Most affected: a2ui-project (1), artbees (1). 1 of 7 new CVEs already have a fix or vendor patch; for the other 6, follow the downgrade or mitigation steps until one ships.
Patch these first
CVE-2026-110879: jackson-databind validates the outer class of a class-name type ID but accepts attacker-selected classes insid
- Risk: Critical (CVSS 9.8), priority 39/100 (patch this month), published 28 October 2026
- Exploitation: attackable over the network without a login
- What to do: apply the vendor mitigation
Why it ranks here: critical severity; remotely exploitable, no login, no user action.
References: NVD
CVE-2026-106013: The Jupiter X Core plugin for WordPress is vulnerable to Authentication Bypass via the Twitter/X Social Login
- Risk: Critical (CVSS 9.8), priority 34/100 (patch this month), published 28 October 2026
- Affected: artbees jupiter x core (<= 4.61.0)
- Fixed in: newer than 4.61.0
- What to do: upgrade to newer than 4.61.0 for artbees jupiter x core
Why it ranks here: critical severity.
References: NVD
CVE-2026-110747: ProtobufParser._readStringKey() reads the length prefix of a protobuf map entry's string key into an attacker-
- Risk: High (CVSS 7.5), priority 31/100 (routine), published 28 October 2026
- Exploitation: attackable over the network without a login
- What to do: apply the vendor mitigation
Why it ranks here: high severity; remotely exploitable, no login, no user action.
References: NVD
CVE-2026-104895: The asynchronous Smile parser (NonBlockingByteArrayParser) uses a raw-binary length prefix taken from untruste
- Risk: High (CVSS 7.5), priority 31/100 (routine), published 28 October 2026
- Exploitation: attackable over the network without a login
- What to do: apply the vendor mitigation
Why it ranks here: high severity; remotely exploitable, no login, no user action.
References: NVD
CVE-2026-104016: ProtobufParser parses length-prefixed protobuf string and bytes fields by checking (_inputPtr + len) <= _input
- Risk: High (CVSS 7.5), priority 31/100 (routine), published 28 October 2026
- Exploitation: attackable over the network without a login
- What to do: apply the vendor mitigation
Why it ranks here: high severity; remotely exploitable, no login, no user action.
References: NVD
CVE-2026-118129: A vulnerability was found in jeremyckahn Chitchatter up to f82538633813c854a81a8b2112a2f6ba17b39cbc
- Risk: Medium (CVSS 6.3), priority 22/100 (routine), published 28 October 2026
- What to do: apply the vendor mitigation
References: NVD
CVE-2026-118271: A security vulnerability has been detected in a2ui-project a2ui up to 0.10.6
- Risk: Medium (CVSS 4.3), priority 15/100 (routine), published 28 October 2026
- Affected: a2ui-project a2ui (0.10.0, 0.10.1, 0.10.2)
- No fix yet, safe release: before 0.10.0
- What to do: downgrade to a release before 0.10.0 until a fix ships for a2ui-project a2ui
References: NVD · Patch · Patch
Most affected vendors
- a2ui-project: 1 new CVE
- artbees: 1 new CVE
How to act on this list
- Start with anything marked exploited or patch now.
- Check what you run: see how to check a version and patch it on Linux, Windows, pip and npm.
- Prefer the vendor or distro fix. If none exists, read when to downgrade and when to mitigate.
- 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 28 October 2026?
CVE-2026-110879 (jackson-databind validates the outer class of a class-name type ID but accepts attacker-selected classes insid) 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.