Usage of unsafe random function in form-data for choosing boundary
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2025-7783
PublishedUse of Insufficiently Random Values vulnerability in form-data allows HTTP Parameter Pollution (HPP). This vulnerability is associated with program files lib/form_data.Js. This issue affects form-data: < 2.5.4, 3.0.0 - 3.0.3, 4.0.0 - 4.0.3.
- Source published
- 18 Jul 2025 16:34:44 UTC
- Source modified
- 3 Nov 2025 20:07:41 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 4.0 · 9.4 CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
euvd · EUVD-2025-21906
PublishedUse of Insufficiently Random Values vulnerability in form-data allows HTTP Parameter Pollution (HPP). This vulnerability is associated with program files lib/form_data.Js. This issue affects form-data: < 2.5.4, 3.0.0 - 3.0.3, 4.0.0 - 4.0.3.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Jul 18, 2025, 4:34:44 PM
dateUpdated: Nov 3, 2025, 8:07:41 PM
37 related source bulletins · separate from aliases
RHSA-2025:23528: Red Hat Security Advisory: multicluster engine for Kubernetes 2.6 security update
CVE-2022-21698 · CVE-2023-44487 · CVE-2025-7195 · CVE-2025-7783 · CVE-2025-9287 · CVE-2025-9288
WID-SEC-W-2025-2165: Qlik Sense: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen
CVE-2025-7783
RHSA-2025:16911: Red Hat Security Advisory: RHACS 4.7 bug fix and security update
CVE-2025-7783
RHSA-2025:14886: Red Hat Security Advisory: Kiali 2.4.8 for Red Hat OpenShift Service Mesh 3.0
CVE-2025-7783
RHSA-2025:19335: Red Hat Security Advisory: Red Hat Advanced Cluster Management for Kubernetes 2.14.1 security update
CVE-2025-7195 · CVE-2025-7783 · CVE-2025-9287 · CVE-2025-9288 · CVE-2025-47907 · CVE-2025-53547 · CVE-2025-58754
openSUSE-SU-2026:11126-1: velociraptor-0.7.0.4.git185.a5708584-2.1 on GA media
CVE-2023-45288 · CVE-2024-45339 · CVE-2025-13465 · CVE-2025-22868 · CVE-2025-22869 · CVE-2025-22870 · CVE-2025-22872 · CVE-2025-24358 · CVE-2025-47911 · CVE-2025-58058 · CVE-2025-58181 · CVE-2025-58190 · CVE-2025-5889 · CVE-2025-64718 · CVE-2025-6545 · CVE-2025-6547 · CVE-2025-7783 · CVE-2026-1229 · CVE-2026-25128 · CVE-2026-25680 · CVE-2026-25681 · CVE-2026-26278 · CVE-2026-26996 · CVE-2026-27136 · CVE-2026-2739 · CVE-2026-27606 · CVE-2026-27904 · CVE-2026-33036 · CVE-2026-33186 · CVE-2026-33487 · CVE-2026-33814 · CVE-2026-34986 · CVE-2026-39821 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-42039 · CVE-2026-42502 · CVE-2026-42506 · CVE-2026-42508 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598
RHSA-2025:21146: Red Hat Security Advisory: Cluster Observability Operator 1.3.0
CVE-2025-2843 · CVE-2025-7783
WID-SEC-W-2025-2150: Red Hat Enterprise Linux: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen
CVE-2025-7783
openSUSE-SU-2026:11680-1: agama-web-ui-24+0.a836cced5-52.1 on GA media
CVE-2025-7783 · CVE-2026-13149 · CVE-2026-13676 · CVE-2026-33245 · CVE-2026-49356 · CVE-2026-53550 · CVE-2026-53632 · CVE-2026-54466 · CVE-2026-55602 · CVE-2026-67313 · CVE-2026-67315 · CVE-2026-67317 · CVE-2026-67319 · CVE-2026-67321 · CVE-2026-69153 · CVE-2026-73086 · CVE-2026-73088 · CVE-2026-73089 · CVE-2026-73650
RHSA-2026:83548: Red Hat Security Advisory: Red Hat Ceph Storage
CVE-2019-10790 · CVE-2023-25153 · CVE-2023-28155 · CVE-2023-46159 · CVE-2024-5206 · CVE-2024-11831 · CVE-2024-37890 · CVE-2024-47866 · CVE-2025-7783 · CVE-2025-30156 · CVE-2025-47914 · CVE-2025-50181 · CVE-2025-50182 · CVE-2025-58181 · CVE-2025-59436 · CVE-2025-64718 · CVE-2025-64756 · CVE-2026-50152
RHSA-2026:41928: Red Hat Security Advisory: Red Hat Migration Toolkit for Containers
CVE-2025-7783 · CVE-2025-12816 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-52881 · CVE-2025-58183 · CVE-2025-58754 · CVE-2025-61726 · CVE-2025-61729 · CVE-2025-62718 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-66506 · CVE-2025-68121 · CVE-2025-69223 · CVE-2025-69227 · CVE-2025-69228 · CVE-2026-4800 · CVE-2026-6322 · CVE-2026-9277 · CVE-2026-9595 · CVE-2026-12143 · CVE-2026-13149 · CVE-2026-13676 · CVE-2026-21441 · CVE-2026-22029 · CVE-2026-23490 · CVE-2026-23745 · CVE-2026-25679 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-27137 · CVE-2026-29063 · CVE-2026-30922 · CVE-2026-32280 · CVE-2026-32281 · CVE-2026-32283 · CVE-2026-33186 · CVE-2026-33810 · CVE-2026-33811 · CVE-2026-34986 · CVE-2026-39820 · CVE-2026-39821 · CVE-2026-40895 · CVE-2026-42264 · CVE-2026-42338 · CVE-2026-42499 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44495 · CVE-2026-44496 · CVE-2026-45736 · CVE-2026-45822 · CVE-2026-48779
WID-SEC-W-2025-2424: IBM Rational Team Concert: Mehrere Schwachstellen
CVE-2024-23337 · CVE-2024-33531 · CVE-2025-22874 · CVE-2025-32379 · CVE-2025-36081 · CVE-2025-36083 · CVE-2025-36085 · CVE-2025-45768 · CVE-2025-48060 · CVE-2025-50181 · CVE-2025-50182 · CVE-2025-53547 · CVE-2025-7338 · CVE-2025-7783 · CVE-2025-9288
RHSA-2025:20047: Red Hat Security Advisory: Red Hat Developer Hub 1.8.0 release.
CVE-2025-7783
msrc_CVE-2025-7783: Usage of unsafe random function in form-data for choosing boundary
CVE-2025-7783
WID-SEC-W-2026-0204: IBM DB2 Big SQL: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen
CVE-2025-7783
RHSA-2026:3406: Red Hat Security Advisory: New container image: rhceph-9.0
CVE-2021-23358 · CVE-2024-45310 · CVE-2024-51744 · CVE-2024-55565 · CVE-2025-6176 · CVE-2025-7783 · CVE-2025-14104 · CVE-2025-22868 · CVE-2025-26791 · CVE-2025-50181 · CVE-2025-50182 · CVE-2025-66418 · CVE-2025-66471 · CVE-2026-21441
RHSA-2025:16918: Red Hat Security Advisory: RHACS 4.7.7 bug fix and security update
CVE-2025-7783
WID-SEC-W-2025-1854: HCL BigFix Komponente: Mehrere Schwachstellen
CVE-2023-3817 · CVE-2023-5678 · CVE-2025-52617 · CVE-2025-52618 · CVE-2025-52619 · CVE-2025-52620 · CVE-2025-52621 · CVE-2025-7338 · CVE-2025-7783
RHSA-2025:19332: Red Hat Security Advisory: multicluster engine for Kubernetes 2.9.1 security update
CVE-2025-7195 · CVE-2025-7783 · CVE-2025-9287 · CVE-2025-9288 · CVE-2025-47907
openSUSE-SU-2025:15380-1: jupyter-nbdime-7.0.2-21.1 on GA media
CVE-2025-7783
RHSA-2025:14919: Red Hat Security Advisory: Red Hat build of Cryostat 4.0.2: new RHEL 9 container image security update
CVE-2025-7783 · CVE-2025-8415 · CVE-2025-55163
RHSA-2025:23529: Red Hat Security Advisory: Red Hat Advanced Cluster Management for Kubernetes 2.11.9 security update
CVE-2023-44487 · CVE-2025-7195 · CVE-2025-7783 · CVE-2025-9287 · CVE-2025-9288
RHSA-2026:59439: Red Hat Security Advisory: RHTAS 1.3.7 - Red Hat Trusted Artifact Signer Release
CVE-2024-9355 · CVE-2025-7783 · CVE-2025-47907 · CVE-2026-48702 · CVE-2026-59869
RHSA-2025:21704: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.20 security, enhancement & bug fix update
CVE-2022-0155 · CVE-2022-0536 · CVE-2024-45338 · CVE-2025-5889 · CVE-2025-7339 · CVE-2025-7783 · CVE-2025-22869
ICSA-26-071-03: Siemens SIDIS Prime
CVE-2024-29857 · CVE-2024-30171 · CVE-2024-30172 · CVE-2024-41996 · CVE-2025-6965 · CVE-2025-7783 · CVE-2025-9230 · CVE-2025-9232 · CVE-2025-9670 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-58751 · CVE-2025-58752 · CVE-2025-58754 · CVE-2025-62522 · CVE-2025-64718 · CVE-2025-64756 · CVE-2025-66030 · CVE-2025-66031 · CVE-2025-66035 · CVE-2025-66412 · CVE-2025-69277 · CVE-2026-22610
RHSA-2026:2800: Red Hat Security Advisory: Red Hat Ceph Storage
CVE-2024-31884 · CVE-2025-6176 · CVE-2025-7783 · CVE-2025-14104 · CVE-2025-66418 · CVE-2025-66471
openSUSE-SU-2025:15373-1: jupyter-jupyterlab-templates-0.5.2-3.1 on GA media
CVE-2025-7783
SUSE-SU-2025:3919-1: Security update for nodejs18
CVE-2025-7783
RHSA-2026:2737: Red Hat Security Advisory: Red Hat Ceph Storage
CVE-2019-10790 · CVE-2021-23358 · CVE-2022-34749 · CVE-2024-31884 · CVE-2024-51744 · CVE-2024-55565 · CVE-2025-6176 · CVE-2025-7783 · CVE-2025-12816 · CVE-2025-14104 · CVE-2025-26791 · CVE-2025-47907 · CVE-2025-47913 · CVE-2025-58183 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-68429
SSA-485750: SSA-485750: Multiple Vulnerabilities in SIDIS Prime Before V4.0.800
CVE-2024-29857 · CVE-2024-30171 · CVE-2024-30172 · CVE-2024-41996 · CVE-2025-6965 · CVE-2025-7783 · CVE-2025-9230 · CVE-2025-9232 · CVE-2025-9670 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-58751 · CVE-2025-58752 · CVE-2025-58754 · CVE-2025-62522 · CVE-2025-64718 · CVE-2025-64756 · CVE-2025-66030 · CVE-2025-66031 · CVE-2025-66035 · CVE-2025-66412 · CVE-2025-69277 · CVE-2026-22610
NCSC-2026-0079: Kwetsbaarheden verholpen in Siemens producten
CVE-2024-29857 · CVE-2024-30171 · CVE-2024-30172 · CVE-2024-41996 · CVE-2025-6965 · CVE-2025-7783 · CVE-2025-9230 · CVE-2025-9232 · CVE-2025-9670 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-27769 · CVE-2025-40943 · CVE-2025-55018 · CVE-2025-58751 · CVE-2025-58752 · CVE-2025-58754 · CVE-2025-62439 · CVE-2025-62522 · CVE-2025-64157 · CVE-2025-64718 · CVE-2025-64756 · CVE-2025-66030 · CVE-2025-66031 · CVE-2025-66035 · CVE-2025-66412 · CVE-2025-69277 · CVE-2026-22610 · CVE-2026-24858 · CVE-2026-25569 · CVE-2026-25570 · CVE-2026-25571 · CVE-2026-25572 · CVE-2026-25573 · CVE-2026-25605
RHSA-2025:15771: Red Hat Security Advisory: RHACS 4.8.4 security and bug fix update
CVE-2025-7783
openSUSE-SU-2026:21448-1: Security update for agama-web-ui
CVE-2025-7783 · CVE-2026-12143 · CVE-2026-13149 · CVE-2026-13311 · CVE-2026-13676 · CVE-2026-27601 · CVE-2026-40181 · CVE-2026-49356 · CVE-2026-53550 · CVE-2026-53632 · CVE-2026-54466 · CVE-2026-54490 · CVE-2026-55602
RHSA-2025:16916: Red Hat Security Advisory: RHACS 4.7 bug fix and security update
CVE-2025-7783
WID-SEC-W-2025-1929: IBM App Connect Enterprise: Mehrere Schwachstellen
CVE-2025-7338 · CVE-2025-7339 · CVE-2025-7783
WID-SEC-W-2026-0559: IBM Rational Build Forge: Mehrere Schwachstellen
CVE-2018-25031 · CVE-2019-17495 · CVE-2021-22060 · CVE-2021-22096 · CVE-2022-22968 · CVE-2022-22970 · CVE-2024-38820 · CVE-2024-38828 · CVE-2025-41248 · CVE-2025-41249 · CVE-2025-48734 · CVE-2025-53057 · CVE-2025-53066 · CVE-2025-58754 · CVE-2025-7783
RHSA-2025:17501: Red Hat Security Advisory: RHOAI 2.24.0 - Red Hat OpenShift AI
CVE-2025-7783 · CVE-2025-10725 · CVE-2025-55163 · CVE-2025-57852
- Source published
- Jul 18, 2025, 4:34:44 PM (timezone not stated)
- Source modified
- Nov 3, 2025, 8:07:41 PM (timezone not stated)
- Saved here
- 15 Nov 2026 12:09:40 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 4.0 · 9.4 CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
nvd · CVE-2025-7783
PublishedUse of Insufficiently Random Values vulnerability in form-data allows HTTP Parameter Pollution (HPP). This vulnerability is associated with program files lib/form_data.Js. This issue affects form-data: < 2.5.4, 3.0.0 - 3.0.3, 4.0.0 - 4.0.3.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Deferred
Weakness classifications: CWE-330
Original publisher date fields
published: 2025-07-18T17:15:44.747
lastModified: 2026-06-17T10:05:39.033
- Source published
- 18 Jul 2025 17:15:44 UTC
- Source modified
- 17 Jun 2026 10:05:39 UTC
- Saved here
- 25 Oct 2026 04:17:18 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 4.0 · 7ffcee3d-2c14-4c3e-b844-86c6a321a158 · Secondary · 9.4 CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
osv · GHSA-fjxv-7rqg-78g4
Published### Summary form-data uses `Math.random()` to select a boundary value for multipart form-encoded data. This can lead to a security issue if an attacker: 1. can observe other values produced by Math.random in the target application, and 2. can control one field of a request made using form-data Because the values of Math.random() are pseudo-random and predictable (see: https://blog.securityevaluators.com/hacking-the-javascript-lottery-80cc437e3b7f), an attacker who can observe a few sequential values can determine the state of the PRNG and predict future values, includes those used to generate form-data's boundary value. The allows the attacker to craft a value that contains a boundary value, allowing them to inject additional parameters into the request. This is largely the same vulnerability as was [recently found in `undici`](https://hackerone.com/reports/2913312) by [`parrot409`](https://hackerone.com/parrot409?type=user) -- I'm not affiliated with that researcher but want to give credit where credit is due! My PoC is largely based on their work. ### Details The culprit is this line here: https://github.com/form-data/form-data/blob/426ba9ac440f95d1998dac9a5cd8d738043b048f/lib/form_data.js#L347 An attacker who is able to predict the output of Math.random() can predict this boundary value, and craft a payload that contains the boundary value, followed by another, fully attacker-controlled field. This is roughly equivalent to any sort of improper escaping vulnerability, with the caveat that the attacker must find a way to observe other Math.random() values generated by the application to solve for the state of the PRNG. However, Math.random() is used in all sorts of places that might be visible to an attacker (including by form-data itself, if the attacker can arrange for the vulnerable application to make a request to an attacker-controlled server using form-data, such as a user-controlled webhook -- the attacker could observe the boundary values from those requests to observe the Math.random() outputs). A common example would be a `x-request-id` header added by the server. These sorts of headers are often used for distributed tracing, to correlate errors across the frontend and backend. `Math.random()` is a fine place to get these sorts of IDs (in fact, [opentelemetry uses Math.random for this purpose](https://github.com/open-telemetry/opentelemetry-js/blob/2053f0d3a44631ade77ea04f656056a2c8a2ae76/packages/opentelemetry-sdk-trace-base/src/platform/node/RandomIdGenerator.ts#L22)) ### PoC PoC here: https://github.com/benweissmann/CVE-2025-7783-poc Instructions are in that repo. It's based on the PoC from https://hackerone.com/reports/2913312 but simplified somewhat; the vulnerable application has a more direct side-channel from which to observe Math.random() values (a separate endpoint that happens to include a randomly-generated request ID). ### Impact For an application to be vulnerable, it must: - Use `form-data` to send data including user-controlled data to some other system. The attacker must be able to do something malicious by adding extra parameters (that were not intended to be user-controlled) to this request. Depending on the target system's handling of repeated parameters, the attacker might be able to overwrite values in addition to appending values (some multipart form handlers deal with repeats by overwriting values instead of representing them as an array) - Reveal values of Math.random(). It's easiest if the attacker can observe multiple sequential values, but more complex math could recover the PRNG state to some degree of confidence with non-sequential values. If an application is vulnerable, this allows an attacker to make arbitrary requests to internal systems.
- Source published
- 21 Jul 2025 19:04:54 UTC
- Source modified
- 10 Sep 2026 03:50:57 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V4 · CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
Publisher rating · CRITICAL