# CWE-1284: Improper Validation of Specified Quantity in Input

> As of 2026-10-05, CWE-1284 (Improper Validation of Specified Quantity in Input) underlies 6 CVEs tracked by Threadlinqs, none of them in the CISA Known Exploited Vulnerabilities catalog, and is cited by 11 tracked threats.

**Last updated:** 2026-10-05

## What is CWE-1284?

The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties.

Specified quantities include size, length, frequency, price, rate, number of operations, time, and others. Code may rely on specified quantities to allocate resources, perform calculations, control iteration, etc.

CWE-1284 is a base-level weakness in MITRE’s Common Weakness Enumeration. Applicable platforms: Not Language-Specific.

_Source: [MITRE CWE](https://cwe.mitre.org/data/definitions/1284.html) (CWE-1284 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data._

## Consequences

- **Other, Integrity, Availability** — Varies by Context, DoS: Resource Consumption (CPU), Modify Memory, Read Memory. When the quantity is not properly validated, then attackers can specify malicious quantities to cause excessive resource allocation, trigger unexpected failures, enable buffer overflows, etc.

_Source: MITRE CWE, common consequences._

## How CWE-1284 is exploited in the wild

Threadlinqs maps 6 CVEs to CWE-1284, published between 2026-06-05 and 2026-10-03. None of them is in the CISA KEV catalog yet. By CVSS v3 severity the set splits into 1 critical, 2 high, 1 medium. The highest EPSS score in the set is 1.6% (CVE-2026-49777), the modelled probability of exploitation in the next 30 days. 11 tracked threats reference CWE-1284 directly or through a CVE it covers; the most recent is “Cosmos EVM Balance-Handling Flaw (GHSA-7g4w-cg88-2cq2) Actively Exploited Across Six Blockchains” (2026-08-28). Affected products concentrate in FOSSBilling (1), OpenBSD (1), ShapedPlugin, LLC (1), among 6 vendors in total.

## Vulnerabilities (CVEs)

All 6 CVEs mapped to CWE-1284, CISA KEV first, then by CVSS score.

- [CVE-2026-49777](https://intel.threadlinqs.com/cve/CVE-2026-49777) — CVSS 10 critical · EPSS 1.6% · published 2026-06-05
- [CVE-2026-103065](https://intel.threadlinqs.com/cve/CVE-2026-103065) — CVSS 8.2 high · published 2026-10-03
- [CVE-2026-82397](https://intel.threadlinqs.com/cve/CVE-2026-82397) — CVSS 7.5 high · EPSS 0.3% · published 2026-08-31
- [CVE-2026-55706](https://intel.threadlinqs.com/cve/CVE-2026-55706) — CVSS 5.8 medium · EPSS 0.2% · published 2026-06-17
- [CVE-2026-43928](https://intel.threadlinqs.com/cve/CVE-2026-43928) — EPSS 0.2% · published 2026-07-06
- [CVE-2026-19026](https://intel.threadlinqs.com/cve/CVE-2026-19026) — EPSS 0.1% · published 2026-08-05

## Affected vendors

- [FOSSBilling](https://intel.threadlinqs.com/vendors/fossbilling) — 1 CVE
- **OpenBSD** — 1 CVE
- **ShapedPlugin, LLC** — 1 CVE
- **The HDF Group** — 1 CVE
- **Themeum** — 1 CVE
- **tornadoweb** — 1 CVE

## Threat activity

11 tracked threats cite CWE-1284:

- [Cosmos EVM Balance-Handling Flaw (GHSA-7g4w-cg88-2cq2) Actively Exploited Across Six Blockchains](https://intel.threadlinqs.com/threat/TL-2026-2194) — CRITICAL · 2026-08-28
- [ServiceNow Patches Four Critical Flaws Including Three CVSS 10.0 Unauthenticated RCE/SQLi Bugs (CVE-2026-18885, CVE-2026-18886, CVE-2026-74820, CVE-2026-6876)](https://intel.threadlinqs.com/threat/TL-2026-2195) — CRITICAL · 2026-08-28
- [Multiple Critical Vulnerabilities in Cisco Catalyst SD-WAN Software (CVE-2026-20303, CVE-2026-20304, CVE-2026-20310, CVE-2026-20312, CVE-2026-20313)](https://intel.threadlinqs.com/threat/TL-2026-1905) — CRITICAL · 2026-08-06
- [OpenAI Models Chain Eight JFrog Artifactory Zero-Days to Escape Sandbox and Breach Hugging Face](https://intel.threadlinqs.com/threat/TL-2026-1750) — CRITICAL · 2026-07-28
- [CVE-2026-14266: 7-Zip Heap-Based Buffer Overflow in XZ Chunk Handling Enables Arbitrary Code Execution](https://intel.threadlinqs.com/threat/TL-2026-1428) — HIGH · 2026-07-16
- [Linux Kernel FUSE Page-Cache Buffer Overflow (CVE-2026-31694) Enables Local Privilege Escalation](https://intel.threadlinqs.com/threat/TL-2026-1177) — HIGH · 2026-07-10
- [ShapedPlugin WordPress Pro Plugins Backdoored via Build-Pipeline Supply Chain Compromise (CVE-2026-49777, CVE-2026-10735)](https://intel.threadlinqs.com/threat/TL-2026-0908) — CRITICAL · 2026-06-22
- [CVE-2026-55706: 27-Year-Old OpenBSD sppp(4) PAP Authentication Bypass in sppp_pap_input()](https://intel.threadlinqs.com/threat/TL-2026-0881) — MEDIUM · 2026-06-17
- [DirtyDecrypt / DirtyCBC — Linux Kernel rxgk Root LPE with Public PoC (CVE-2026-31635)](https://intel.threadlinqs.com/threat/TL-2026-0524) — HIGH · 2026-05-18
- [Fragnesia — DirtyFrag-Family Linux Kernel LPE via XFRM ESP-in-TCP Page-Cache Corruption](https://intel.threadlinqs.com/threat/TL-2026-0510) — HIGH · 2026-05-13
- [CVE-2023-42282 (npm 'ip' package IP-validation flaw) reignites maintainer-vs-researcher CVE severity dispute](https://intel.threadlinqs.com/threat/TL-2026-1536) — MEDIUM · 2026-02-16

## Mitigations

- **Implementation / Input Validation**: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid

_Source: MITRE CWE, potential mitigations._

## Detection methods (MITRE CWE)

- **Automated Static Analysis**: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

_Source: MITRE CWE, detection methods. Threadlinqs detection rules for the threats above are Blue tier and higher._

## Related weaknesses

- [CWE-20 Improper Input Validation](https://intel.threadlinqs.com/cwe/CWE-20)
- [CWE-789](https://cwe.mitre.org/data/definitions/789.html)

Canonical: https://intel.threadlinqs.com/cwe/CWE-1284
Source definition: https://cwe.mitre.org/data/definitions/1284.html
Detection rules and IOCs for threats exploiting CWE-1284 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp
