PULSE
FEED
ransomplay reclama a Minor League Baseball · US · Hospitalityransomn0n reclama a Company #213 · QAransomn0n reclama a Company #212 · ETransomdoommageddon reclama a K**** T**** H**** B****ransomcurious worm reclama a sacheminc.com · CA · Manufacturingransomcurious worm reclama a sbhny.org · USransomcurious worm reclama a shannonhealth.com · IE · Healthcareransomcurious worm reclama a baronandbudd.com · GB · Professional Servicesransomeverstake reclama a ki*****o.comransomcurious worm reclama a raleighortho.com · US · Healthcareransomcurious worm reclama a lifelinescreening.com · US · Healthcareransomcurious worm reclama a safcodental.com · SA · Healthcareransomcurious worm reclama a marquiscompanies.com · US · Professional Servicesransomcurious worm reclama a atlashp.com · Technologyransomplay reclama a Minor League Baseball · US · Hospitalityransomn0n reclama a Company #213 · QAransomn0n reclama a Company #212 · ETransomdoommageddon reclama a K**** T**** H**** B****ransomcurious worm reclama a sacheminc.com · CA · Manufacturingransomcurious worm reclama a sbhny.org · USransomcurious worm reclama a shannonhealth.com · IE · Healthcareransomcurious worm reclama a baronandbudd.com · GB · Professional Servicesransomeverstake reclama a ki*****o.comransomcurious worm reclama a raleighortho.com · US · Healthcareransomcurious worm reclama a lifelinescreening.com · US · Healthcareransomcurious worm reclama a safcodental.com · SA · Healthcareransomcurious worm reclama a marquiscompanies.com · US · Professional Servicesransomcurious worm reclama a atlashp.com · Technology
← All CVEs
CVE WatchNov 11, 2026

CVE-2026-126230

A use of externally-controlled format string vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.1, FortiAnalyzer 7.6.0 through 7.6.7,

CVSS

7.2

High

EPSS

—

KEV

—

Exploit Today

—

0-100

Published: Nov 11, 2026 · Last modified: Nov 11, 2026 · CWE-134

EPSS · 30d

Not enough EPSS history yet.

Technical description

A use of externally-controlled format string vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.1, FortiAnalyzer 7.6.0 through 7.6.7, FortiAnalyzer 7.4.0 through 7.4.11, FortiAnalyzer 7.2.0 through 7.2.12, FortiAnalyzer Cloud 8.0.0 through 8.0.1, FortiAnalyzer Cloud 7.6.0 through 7.6.7, FortiAnalyzer Cloud 7.4.1 through 7.4.11, FortiAnalyzer Cloud 7.2.1 through 7.2.12, FortiManager 8.0.0 through 8.0.1, FortiManager 7.6.0 through 7.6.7, FortiManager 7.4.0 through 7.4.11, FortiManager 7.2.0 through 7.2.12, FortiManager Cloud 8.0.0 through 8.0.1, FortiManager Cloud 7.6.0 through 7.6.7, FortiManager Cloud 7.4.1 through 7.4.11, FortiManager Cloud 7.2.1 through 7.2.12 may allow an authenticated administrator to execute unauthorized code or commands or cause a denial of service via specially crafted requests.

Official references
Related CVEs
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-1262477.2 HIG
—
———A use of externally-controlled format string vulnerability in Fortinet FortiAuthenticator 8.0.0 through 8.0.3, FortiAuthenticator 6.6.0 through 6.6.10 may allow an authenticated privileged attacker to execute unauthorized code or commands via http requests.4h
CVE-2026-1261717.2 HIG
—
———A use of externally-controlled format string vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.1, FortiAnalyzer 7.6.0 through 7.6.7, FortiAnalyzer 7.4.0 through 7.4.11, FortiAnalyzer 7.2.0 through 7.2.12, FortiAnalyzer Cloud 8.0.1, FortiAnalyzer Cloud 7.6.0 through 7.6.7, FortiAnalyzer Cloud 7.4.1 through 7.4.11, FortiAnalyzer Cloud 7.2.1 through 7.2.12, FortiManager 8.0.0 through 8.0.1, FortiManager 7.6.0 through 7.6.7, FortiManager 7.4.0 through 7.4.11, FortiManager 7.2.0 through 7.2.12, FortiManager Cloud 8.0.1, FortiManager Cloud 7.6.0 through 7.6.7, FortiManager Cloud 7.4.1 through 7.4.11, FortiManager Cloud 7.2.1 through 7.2.12 may allow an authenticated attacker to execute unauthorized commands via specially crafted HTTP request4h
CVE-2026-1261638.1 HIG
—
———A use of externally-controlled format string vulnerability in Fortinet FortiMail 8.0.0 through 8.0.1 may allow a remote unauthenticated attacker to execute unauthorized code or commands via a specially crafted SMTP command.4h
CVE-2026-1055845.5 MED
39.6%
——12Use of externally-controlled format string in Windows Inventory Backup allows an authorized attacker to disclose information locally.1d
CVE-2026-1200596.8 MED
18.0%
——5For an updatable cursor over a table without OIDs that has an auto-increment int4 column, psqlODBC places that column's name, as reported by the server, into a printf-style format string. It later expands that string with one argument while it builds the WHERE clause of its positioned SELECT, UPDATE, and DELETE statements. A column name that contains format directives makes the driver read unrelated memory, which can crash the application or copy client memory into query text sent to the server. The name can come from a server not trusted under current SSL settings, or from any database user who can create a table that the application reads with an updatable cursor. Versions before psqlODBC 18.00.0006 are affected.9d
CVE-2026-63201—
38.0%
——11Netopeer2 is a server for implementing network configuration management based on the `NETCONF` Protocol. In affected versions, a low-privileged authenticated `NETCONF` user can remotely crash `netopeer2-server` by sending a `get RPC` with an invalid `subtree filter` whose text contains format specifiers. In `src/netconf.c`, `np2srv_rpc_get_cb()` sends the invalid value through `ERR()` to `np2log_printf()`, where `vsnprintf()` first formats the message safely. In `src/log.c`, that already formatted buffer is subsequently passed to `np2log()` as the format string itself, causing `vsyslog()` to interpret attacker-controlled percent sequences and read invalid pointer arguments. The reported denial of service was confirmed on version 2.8.7 using `NETCONF`-over-SSH and AddressSanitizer; reliable remote code execution was not confirmed. `The advisory identifies 2.8.8 as patched`; repository comparisons verify the fix in public release 2.8.21. The affected/fixed boundary remains unresolved because no public 2.8.8 tag was located, which does not establish the status of an untagged 2.8.8 build.9d