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

CVE-2026-116117 halo-dev halo up: top risk today, fix steps

On 26 October 2026, 12 new CVEs were published that we track: 0 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-116117 (high, CVSS 7.3, priority 31/100). Recommended action: apply the vendor mitigation. 2 of the 8 top items can be attacked remotely without a login. Most affected: n a (4). 0 of 12 new CVEs already have a fix or vendor patch; for the other 12, follow the downgrade or mitigation steps until one ships.

Patch these first

CVE-2026-116117: A flaw has been found in halo-dev halo up to 2.27.0-beta.1

High severity (CVSS 7.3), priority 31/100 (routine). Signals: high severity; remotely exploitable, no login, no user action. Recommended action: apply the vendor mitigation.

References: NVD

CVE-2026-116116: A vulnerability was detected in Yoosee GM8135S Camera 21.00.01.36

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

References: NVD

CVE-2026-113345: Electronic delivery item Inspection Support System provided by Japan's Ministry of Land, Infrastructure, Trans

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

References: NVD

CVE-2026-116118: A vulnerability has been found in Z.ai Zcode up to 3.14.3/3.15.1

Medium severity (CVSS 6.3), priority 22/100 (routine). Recommended action: apply the vendor mitigation.

References: NVD

CVE-2026-116113: A security flaw has been discovered in GouGuOA up to 6.1.2

Medium severity (CVSS 6.3), priority 22/100 (routine). Recommended action: apply the vendor mitigation.

References: NVD

CVE-2026-116120: A vulnerability was determined in NocoDB up to 2026.07.0

Medium severity (CVSS 5.6), priority 20/100 (routine). Recommended action: downgrade to a release before 2026.07 until a fix ships for n a nocodb.

References: NVD

CVE-2026-116119: A vulnerability was found in NocoDB up to 2026.08.0

Medium severity (CVSS 5.5), priority 19/100 (routine). Recommended action: apply the vendor mitigation.

References: NVD

CVE-2026-116114: A weakness has been identified in Yoosee GM8135S Camera 21.00.01.36

Low severity (CVSS 3.7), priority 18/100 (routine). Signals: remotely exploitable, no login, no user action. Recommended action: apply the vendor mitigation.

References: NVD

Most affected vendors

• n a: 4 new CVEs

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 26 October 2026?

CVE-2026-116117 (A flaw has been found in halo-dev halo up to 2.27.0-beta.1) ranks highest, with a priority score of 31/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