voxell vciy
CVE-2023-44487
MATERIALCISA KEV
An authority record changed. This is a change in what is asserted about exploitation, not in how the vulnerability is described.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- CISA requires: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. The federal deadline has passed: overdue since 2023-10-31. CISA KEVCISA's notes for this entry: blog.cloudflare.com cisa.gov
- Upgrade to the fixed version for your release line, or later: sinec ins 1.0; windows 10.0.14393.6351; windows 10.0.17763.4974; windows 10.0.19044.3570; windows 10.0.19045.3570; windows 10.0.22000.2538 upper bounds of the CVE record's affected ranges
- Later advisories still cover the fixes above and name higher ones: apisix 3.9.0 (CVE-2025-27446), 3.12.0 (CVE-2025-46647), 3.14.0 (CVE-2025-62232), 3.16.0 (CVE-2026-31908), 3.16.0 (CVE-2026-31923), 3.16.0 (CVE-2026-31924), 3.17.0 (CVE-2026-39998), 3.17.0 (CVE-2026-39999), 3.17.0 (CVE-2026-44046), 3.17.0 (CVE-2026-44087), 3.17.0 (CVE-2026-44915), 3.17.0 (CVE-2026-47339), 3.17.0 (CVE-2026-48895), 3.18.0 (CVE-2026-49231), 3.17.0 (CVE-2026-49871), 3.17.0 (CVE-2026-49872), 3.18.0 (CVE-2026-74848), 3.18.0 (CVE-2026-75020) OSV advisories
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
- weakness
- Not named by the CNA. NVD maps it to CWE-400.
- affected
- Not named by the CNA. The published ranges name Ietf http; Apache tomcat; Siemens sinec ins; and 114 more.
- published ranges
- siemens simatic s7-1500 cpu 1518f-4 pn\/dp mfp firmware >= 3.1.5; siemens sinec ins < 1.0; siemens sinec ins 1.0; siemens sinec ins 1.0-sp1; and 251 more on the CVE page
- first unaffected version, by branch
- sinec ins 1.0; windows 10.0.14393.6351; windows 10.0.17763.4974; windows 10.0.19044.3570; windows 10.0.19045.3570; windows 10.0.22000.2538
- fixed by package (from OSV advisories)
- apisix (Bitnami): 3.6.1 BIT-apisix-2023-44487aspnet-core (Bitnami): 6.0.23; 7.0.12 BIT-aspnet-core-2023-44487contour (Bitnami): 1.24.6 BIT-contour-2023-44487dotnet (Bitnami): 6.0.23; 7.0.12 BIT-dotnet-2023-44487dotnet-sdk (Bitnami): 6.0.23; 7.0.12 BIT-dotnet-sdk-2023-44487envoy (Bitnami): 1.24.12; 1.25.11; 1.26.6; 1.27.2 BIT-envoy-2023-44487and 21 more packages in the OSV advisories
- later fixes (from OSV advisories)
- apisix 3.6.1 is inside a range CVE-2025-27446 (BIT-apisix-2025-27446) lists as affected. That advisory is fixed in 3.9.0.apisix 3.6.1 is inside a range CVE-2025-46647 (BIT-apisix-2025-46647) lists as affected. That advisory is fixed in 3.12.0.apisix 3.6.1 is inside a range CVE-2025-62232 (BIT-apisix-2025-62232) lists as affected. That advisory is fixed in 3.14.0.apisix 3.6.1 is inside a range CVE-2026-31908 (BIT-apisix-2026-31908) lists as affected. That advisory is fixed in 3.16.0.apisix 3.6.1 is inside a range CVE-2026-31923 (BIT-apisix-2026-31923) lists as affected. That advisory is fixed in 3.16.0.apisix 3.6.1 is inside a range CVE-2026-31924 (BIT-apisix-2026-31924) lists as affected. That advisory is fixed in 3.16.0.
- assigned by
- mitre
- published
- 2023-10-10
check us github.com blog.cloudflare.com aws.amazon.com cloud.google.com
Authority held, dated
- CISA KEV
- listed
- added
- 2023-10-10
- remediation due
- 2023-10-31
- ransomware use
- unknown
- remediation status
- overdue since 2023-10-31
- exploit code
- 26 public proof-of-concept repositories, first seen 2023-10-10 (PoC-in-GitHub).
A KEV listing is an assertion of observed exploitation. It is the only element on this page that makes that claim.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 11 Oct 2023 | 0.00195 | |
| 12 Oct 2023 | 0.00636 | |
| 14 Oct 2023 | 0.61208 | crossed 0.10, crossed 0.50 |
| 19 Oct 2023 | 0.52534 | |
| 17 Mar 2025 | 0.89215 | scoring model v2025.03.14 |
| 19 Mar 2025 | 0.90392 | crossed 0.90 |
| 20 Mar 2025 | 0.89215 | crossed 0.90 |
| 23 Mar 2025 | 0.90392 | crossed 0.90 |
| 25 Mar 2025 | 0.89215 | crossed 0.90 |
| 27 Mar 2025 | 0.91023 | crossed 0.90 |
| 8 Jun 2026 | 0.944 | |
| 10 Jun 2026 | 0.94394 | |
| 11 Jun 2026 | 0.9439 | |
| 15 Jun 2026 | 0.99999 | scoring model v2026.06.15 |
168 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Listed, added 2023-10-10. Due 2023-10-31. A changed deadline or a change in ransomware use changes this brief.
- exploit probability
- 1.00 on 2026-06-15 (FIRST's EPSS, a probability and not evidence of exploitation). It is above the top band line, 90%.
- fix
- Held: sinec ins 1.0; windows 10.0.14393.6351; windows 10.0.17763.4974; windows 10.0.19044.3570; windows 10.0.19045.3570; windows 10.0.22000.2538. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2023-44487', '2026-10-29T23:59:59.999999Z', now());