Haskell
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in any Haskell product.
RSS Feeds for Haskell security vulnerabilities
Create a CVE RSS feed including security vulnerabilities found in Haskell products with stack.watch. Just hit watch, then grab your custom RSS feed url.
Products by Haskell Sorted by Most Security Vulnerabilities since 2018
By the Year
In 2025 there have been 0 vulnerabilities in Haskell. Last year, in 2024 Haskell had 1 security vulnerability published. Right now, Haskell is on track to have less security vulnerabilities in 2025 than it did last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2025 | 0 | 0.00 |
| 2024 | 1 | 9.80 |
| 2023 | 0 | 0.00 |
| 2022 | 2 | 7.00 |
It may take a day or so for new Haskell vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Haskell Security Vulnerabilities
| CVE | Date | Vulnerability | Products |
|---|---|---|---|
| CVE-2024-3566 | Apr 10, 2024 |
CVE-2024-3566: CreateProcessBased Command Injection in Windows AppsA command inject vulnerability allows an attacker to perform command injection on Windows applications that indirectly depend on the CreateProcess function when the specific conditions are satisfied. |
|
| CVE-2021-4249 | Dec 18, 2022 |
A vulnerability was found in xml-conduitA vulnerability was found in xml-conduit. It has been classified as problematic. Affected is an unknown function of the file xml-conduit/src/Text/XML/Stream/Parse.hs of the component DOCTYPE Entity Expansion Handler. The manipulation leads to infinite loop. It is possible to launch the attack remotely. Upgrading to version 1.9.1.0 is able to address this issue. The name of the patch is 4be1021791dcdee8b164d239433a2043dc0939ea. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-216204. |
|
| CVE-2022-3433 | Oct 10, 2022 |
The aeson library is not safe to use to consume untrusted JSON inputThe aeson library is not safe to use to consume untrusted JSON input. A remote user could abuse this flaw to produce a hash collision in the underlying unordered-containers library by sending specially crafted JSON data, resulting in a denial of service. |
|