apcupsd up to 3.14.14 src/cgi/upsfetch.c getupsvar uninitialized variable
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.80- |
Summary
A vulnerability was found in apcupsd up to 3.14.14. It has been classified as problematic. This impacts the function getupsvar of the file src/cgi/upsfetch.c. Performing a manipulation results in uninitialized variable.
This vulnerability is cataloged as CVE-2026-103436. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in apcupsd up to 3.14.14. It has been classified as problematic. This affects the function getupsvar of the file src/cgi/upsfetch.c. The manipulation with an unknown input leads to a uninitialized variable vulnerability. CWE is classifying the issue as CWE-457. The code uses a variable that has not been initialized, leading to unpredictable or unintended results. This is going to have an impact on confidentiality. The summary by CVE is:
apcupsd through 3.14.14 discloses uninitialized stack memory in getupsvar() in src/cgi/upsfetch.c (used by upsstats.cgi, multimon.cgi, and upsfstats.cgi. On the single-field path, when the matched STATUS line has fewer than three whitespace-separated tokens, sscanf("%*s %*s %s", answer) performs no assignment but the function returns success, and thus the caller prints the uninitialized destination buffer into the HTTP response.
It is possible to read the advisory at bugzilla.redhat.com. This vulnerability is uniquely identified as CVE-2026-103436 since 09/30/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/30/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.7
CNA Vector (MITRE): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Uninitialized variableCWE: CWE-457 / CWE-453
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
09/30/2026 Advisory disclosed09/30/2026 CVE reserved
09/30/2026 VulDB entry created
09/30/2026 VulDB entry last update
Sources
Advisory: bugzilla.redhat.comStatus: Not defined
CVE: CVE-2026-103436 (🔒)
GCVE (CVE): GCVE-0-2026-103436
GCVE (VulDB): GCVE-100-412179
Entry
Created: 09/30/2026 18:07Changes: 09/30/2026 18:07 (63)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.