Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-103432 – Stack-Based Buffer Overflow (RCE) – apcupsd CGI Modules through 3.14.14

Be the first to know when new zero-days emerge:

Summary

CVE-2026-103432 is a stack-based buffer overflow (CWE-121) in the getupsvar() function used by apcupsd’s CGI modules, affecting apcupsd through version 3.14.14. An unbounded sscanf() call copies attacker-influenced data from a Network Information Server (NIS) response into a fixed-size stack buffer without a width limit, and in some cases the same function can return success while leaving the destination buffer uninitialized. The issue is rated HIGH severity (CVSS 8.1) and is remotely exploitable with no authentication or user interaction.

Technical details

  • Root cause: getupsvar() in src/cgi/upsfetch.c uses sscanf() without a field width limit when parsing data returned by a UPS NIS server, allowing it to write beyond fixed-size (e.g. 256-byte) caller buffers.
  • A related code path in the same function can leave the destination buffer uninitialized while still signaling success, leaking stack memory into the HTTP response.
  • Trigger conditions: the vulnerable CGI binaries (upsstats.cgi, multimon.cgi, upsfstats.cgi) must be reachable via a web server, and the attacker controls or can spoof a UPS host that the CGI queries over the NIS protocol — this includes the default case where hosts.conf is absent/empty and all hosts are implicitly trusted.
  • Attack vector: network, no privileges or user interaction required; the attacker interacts with the CGI over HTTP, which in turn queries an attacker-controlled or spoofed NIS host.
  • Impact: denial of service (CGI process crash), disclosure of uninitialized stack memory in HTTP responses, and overflow primitives that could enable remote code execution, though full RCE has not been publicly demonstrated.
  • This issue is noted as related to CVE-2026-15544. The equivalent daemon-side code in src/drivers/net/net.c was previously hardened with width-limited format strings and loop bounds; that fix has not been applied to the CGI code path.

Affected software

  • apcupsd (apcupsd-cgi component): all versions through 3.14.14, including the CGI binaries upsstats.cgi, multimon.cgi, and upsfstats.cgi.

Severity

  • CVSS v3.1 Base Score: 8.1 (High)
  • Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: No official upstream patch is available — apcupsd has not published a release since 2016. Apply the equivalent width-limited sscanf() fix from the daemon’s src/drivers/net/net.c to src/cgi/upsfetch.c and rebuild, or obtain a distribution/vendor-backported package if one is issued.
  • If no patch can be applied: disable or remove the affected CGI binaries (upsstats.cgi, multimon.cgi, upsfstats.cgi) from the web server, or restrict access to them (authentication, IP allow-listing, or placing them behind a VPN).
  • Configure hosts.conf with an explicit, restrictive list of trusted UPS/NIS hosts rather than relying on the default allow-all behavior.
  • Restrict network exposure of the web server hosting the apcupsd CGI interface so it is not reachable from untrusted networks or the public internet.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge