<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from osv_haskell</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 22 Nov 2026 14:19:45 +0000</lastBuildDate>
    <item>
      <title>HSEC-2026-0016 — Improper IP address validation in validateCertificateName</title>
      <link>https://vulnerability.circl.lu/vuln/hsec-2026-0016</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: crypton-x509-validation&lt;/p&gt;
&lt;p&gt;# Improper IP address validation in validateCertificateName&lt;/p&gt;
&lt;p&gt;`Data.X509.Validation.getNames` extracts only `AltNameDNS` entries from the
subjectAltName extension (Data/X509/Validation.hs, `unAltName`,
~L512–515 in crypton-x509-validation 1.10.1). When a certificate carries an
`iPAddress` SAN but no `dNSName` SAN, the extracted name list is empty, so
`validateNames` (~L569–580) falls through to the commonName branch as if no
SAN extension existed, even though the extension&amp;#39;s haddock promises that the
commonName is ignored whenever subjectAltName is present. Consequently, when
a client connects to an IP literal:&lt;/p&gt;
&lt;p&gt;* a certificate with `CN = &amp;lt;target IP&amp;gt;` but `iPAddress` SAN pointing to a
  different host is **accepted**;
* a certificate whose only valid identity is a matching `iPAddress` SAN is
  **rejected**.&lt;/p&gt;
&lt;p&gt;Exploitation requires a certificate from a CA the client trusts that has a
commonName different from its iPAddress SAN (public CAs are barred from this
by the CA/Browser Forum Baseline Requirements, but private or enterprise
CAs can issue such certificates). A successful impersonation exposes and can
modify the protected connection.&lt;/p&gt;
&lt;p&gt;The draft fix makes `getNames` distinguish &amp;#34;no SAN extension&amp;#34; from &amp;#34;SAN
extension present with no DNS names&amp;#34; and applies SAN semantics (including
the existing iPAddress comparison) whenever the extension is present,
restoring the documented SAN-supersedes-CN behavior in line with RFC 9525.
No fixed release is published at the time of writing…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: crypton-x509-validation&lt;/p&gt;
&lt;p&gt;# Improper IP address validation in validateCertificateName&lt;/p&gt;
&lt;p&gt;`Data.X509.Validation.getNames` extracts only `AltNameDNS` entries from the
subjectAltName extension (Data/X509/Validation.hs, `unAltName`,
~L512–515 in crypton-x509-validation 1.10.1). When a certificate carries an
`iPAddress` SAN but no `dNSName` SAN, the extracted name list is empty, so
`validateNames` (~L569–580) falls through to the commonName branch as if no
SAN extension existed, even though the extension&amp;#39;s haddock promises that the
commonName is ignored whenever subjectAltName is present. Consequently, when
a client connects to an IP literal:&lt;/p&gt;
&lt;p&gt;* a certificate with `CN = &amp;lt;target IP&amp;gt;` but `iPAddress` SAN pointing to a
  different host is **accepted**;
* a certificate whose only valid identity is a matching `iPAddress` SAN is
  **rejected**.&lt;/p&gt;
&lt;p&gt;Exploitation requires a certificate from a CA the client trusts that has a
commonName different from its iPAddress SAN (public CAs are barred from this
by the CA/Browser Forum Baseline Requirements, but private or enterprise
CAs can issue such certificates). A successful impersonation exposes and can
modify the protected connection.&lt;/p&gt;
&lt;p&gt;The draft fix makes `getNames` distinguish &amp;#34;no SAN extension&amp;#34; from &amp;#34;SAN
extension present with no DNS names&amp;#34; and applies SAN semantics (including
the existing iPAddress comparison) whenever the extension is present,
restoring the documented SAN-supersedes-CN behavior in line with RFC 9525.
No fixed release is published at the time of writing…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/hsec-2026-0016</guid>
      <pubDate>Tue, 17 Nov 2026 09:58:05 +0000</pubDate>
    </item>
    <item>
      <title>HSEC-2026-0017 — Out-of-bounds writes in BMP RLE and TIFF strip decoding</title>
      <link>https://vulnerability.circl.lu/vuln/hsec-2026-0017</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: JuicyPixels&lt;/p&gt;
&lt;p&gt;# Out-of-bounds writes in BMP RLE and TIFF strip decoding&lt;/p&gt;
&lt;p&gt;JuicyPixels contains independent out-of-bounds writes reachable from ordinary
image decoding (`Codec.Picture.decodeImage` and the format-specific decoders):&lt;/p&gt;
&lt;p&gt;1. **BMP `BI_RLE8`/`BI_RLE4`** (`Codec.Picture.Bitmap.decodeImageY8RLE`): the
   pixel buffer size is computed with 32-bit `Int32` arithmetic and wraps to a
   zero-length allocation for large headers; end-of-line and vertical-delta
   control codes move the destination cursor without a bound, and the
   horizontal delta jump is unclamped. Every run writes attacker-chosen bytes
   through `M.unsafeWrite` at the cursor position — negative offsets before
   the raster, arbitrary offsets against a wrapped allocation, and up to 255
   bytes past it.
2. **TIFF uncompressed/PackBits contiguous strips**
   (`Codec.Picture.Tiff.gatherStrips`, `copyByteString`, `unpackPackBit`):
   strip copies have no destination bound and the per-strip size computation
   wraps negative for strips starting past the raster, so excess strips copy
   attacker-chosen bytes past the end of the allocated raster.&lt;/p&gt;
&lt;p&gt;Impact: heap memory adjacent to the decoded image is corrupted with
attacker-selected values and offsets through maliciously crafted BMP or TIFF
files. Beyond corruption, exploitation primitives were demonstrated
end-to-end on GHC 9.6 / linux-amd64: a crafted BMP deterministically crashed
the process via the wrapped allocation; against a warp-based service a single
uploaded BMP over…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: JuicyPixels&lt;/p&gt;
&lt;p&gt;# Out-of-bounds writes in BMP RLE and TIFF strip decoding&lt;/p&gt;
&lt;p&gt;JuicyPixels contains independent out-of-bounds writes reachable from ordinary
image decoding (`Codec.Picture.decodeImage` and the format-specific decoders):&lt;/p&gt;
&lt;p&gt;1. **BMP `BI_RLE8`/`BI_RLE4`** (`Codec.Picture.Bitmap.decodeImageY8RLE`): the
   pixel buffer size is computed with 32-bit `Int32` arithmetic and wraps to a
   zero-length allocation for large headers; end-of-line and vertical-delta
   control codes move the destination cursor without a bound, and the
   horizontal delta jump is unclamped. Every run writes attacker-chosen bytes
   through `M.unsafeWrite` at the cursor position — negative offsets before
   the raster, arbitrary offsets against a wrapped allocation, and up to 255
   bytes past it.
2. **TIFF uncompressed/PackBits contiguous strips**
   (`Codec.Picture.Tiff.gatherStrips`, `copyByteString`, `unpackPackBit`):
   strip copies have no destination bound and the per-strip size computation
   wraps negative for strips starting past the raster, so excess strips copy
   attacker-chosen bytes past the end of the allocated raster.&lt;/p&gt;
&lt;p&gt;Impact: heap memory adjacent to the decoded image is corrupted with
attacker-selected values and offsets through maliciously crafted BMP or TIFF
files. Beyond corruption, exploitation primitives were demonstrated
end-to-end on GHC 9.6 / linux-amd64: a crafted BMP deterministically crashed
the process via the wrapped allocation; against a warp-based service a single
uploaded BMP over…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/hsec-2026-0017</guid>
      <pubDate>Tue, 17 Nov 2026 09:55:51 +0000</pubDate>
    </item>
    <item>
      <title>HSEC-2026-0015 — Missing validation of CONNECT requests in http2</title>
      <link>https://vulnerability.circl.lu/vuln/hsec-2026-0015</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: http2&lt;/p&gt;
&lt;p&gt;# Missing validation of CONNECT requests in http2&lt;/p&gt;
&lt;p&gt;For CONNECT requests, `checkRequestHeader` (`Network/HTTP2/H2/HPACK.hs`) in http2 up to 5.4.13 returned early, only requiring the absence of `:scheme` and `:path`. Every other check was skipped:&lt;/p&gt;
&lt;p&gt;* the requirement that `:authority` is present (RFC 9113, Section 8.5);
* the check that `:authority` and `Host` agree, which applies to every other request (RFC 9113, Section 8.3.1: a server SHOULD treat a mismatch as malformed);
* the common checks for `:status`, `Connection` and `TE`.&lt;/p&gt;
&lt;p&gt;A CONNECT request carrying `:authority: a.example` and `Host: b.example` was therefore accepted. Consumers that read `Host` see `b.example` where intermediaries that read `:authority` see `a.example`. warp, for example, sets `requestHeaderHost` to `Host` when present and falls back to `:authority`, so an application behind an intermediary that routes or authorizes on `:authority` handles a request other than the one the intermediary validated — a request can be smuggled past the front-end&amp;#39;s access control, validation, logging or WAF rules.&lt;/p&gt;
&lt;p&gt;Exploitation requires a front-end that makes decisions based on `:authority` while the application behind it bases routing or authorization on `Host`; a directly exposed server sees only one authority.&lt;/p&gt;
&lt;p&gt;A CONNECT request with neither `:authority` nor `:path` also passed validation and reached warp 3.4.21, where `fromJust (mPath &amp;lt;|&amp;gt; mAuth)` (`Network/Wai/Handler/Warp/HTTP2/Request.hs`) threw. The exception was ra…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: http2&lt;/p&gt;
&lt;p&gt;# Missing validation of CONNECT requests in http2&lt;/p&gt;
&lt;p&gt;For CONNECT requests, `checkRequestHeader` (`Network/HTTP2/H2/HPACK.hs`) in http2 up to 5.4.13 returned early, only requiring the absence of `:scheme` and `:path`. Every other check was skipped:&lt;/p&gt;
&lt;p&gt;* the requirement that `:authority` is present (RFC 9113, Section 8.5);
* the check that `:authority` and `Host` agree, which applies to every other request (RFC 9113, Section 8.3.1: a server SHOULD treat a mismatch as malformed);
* the common checks for `:status`, `Connection` and `TE`.&lt;/p&gt;
&lt;p&gt;A CONNECT request carrying `:authority: a.example` and `Host: b.example` was therefore accepted. Consumers that read `Host` see `b.example` where intermediaries that read `:authority` see `a.example`. warp, for example, sets `requestHeaderHost` to `Host` when present and falls back to `:authority`, so an application behind an intermediary that routes or authorizes on `:authority` handles a request other than the one the intermediary validated — a request can be smuggled past the front-end&amp;#39;s access control, validation, logging or WAF rules.&lt;/p&gt;
&lt;p&gt;Exploitation requires a front-end that makes decisions based on `:authority` while the application behind it bases routing or authorization on `Host`; a directly exposed server sees only one authority.&lt;/p&gt;
&lt;p&gt;A CONNECT request with neither `:authority` nor `:path` also passed validation and reached warp 3.4.21, where `fromJust (mPath &amp;lt;|&amp;gt; mAuth)` (`Network/Wai/Handler/Warp/HTTP2/Request.hs`) threw. The exception was ra…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/hsec-2026-0015</guid>
      <pubDate>Mon, 16 Nov 2026 02:22:07 +0000</pubDate>
    </item>
    <item>
      <title>HSEC-2026-0014 — Arbitrary file write via path traversal in unpackToDir</title>
      <link>https://vulnerability.circl.lu/vuln/hsec-2026-0014</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: libarchive&lt;/p&gt;
&lt;p&gt;# Arbitrary file write via path traversal in unpackToDir&lt;/p&gt;
&lt;p&gt;`Codec.Archive.unpackToDir` extracts a tar (or other archive supported by the
libarchive C library) from a `ByteString` into a directory. `unpackToDirLazy`
is the streaming variant; both funnel through the same internal
`unpackEntriesFp` routine.&lt;/p&gt;
&lt;p&gt;`unpackEntriesFp` joined each entry&amp;#39;s name onto the destination directory with
`System.FilePath.(&amp;lt;/&amp;gt;)` without validating the name. Entry names starting with
`..` sequences therefore escape the destination: `fp &amp;lt;/&amp;gt; &amp;#34;../../../../etc/x&amp;#34;`
resolves outside the extraction root. The joined path is written back into the
archive entry (`archiveEntrySetPathname`) and handed to libarchive&amp;#39;s
`archive_read_extract` with no `ARCHIVE_EXTRACT_SECURE_*` flags, so neither the
Haskell layer nor the C library rejects the traversal. The `..` check is not
limited to tar archives: any format whose entry names libarchive reports
verbatim is affected. Extraction result codes were also discarded, so write
failures could pass unnoticed.&lt;/p&gt;
&lt;p&gt;An attacker who can supply an archive to a service that extracts it with these
APIs gains an arbitrary file write with the privileges of the extracting
process. A demonstrated escalation (verified in a container): an archive with
member `../../../../etc/profile.d/zz-poc-zipslip.sh` plants a shell script
sourced by every subsequent login shell, converting the file write into code
execution when any user logs in.&lt;/p&gt;
&lt;p&gt;The reported traversal is fixed in libarchive-3.0.6.0,…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: libarchive&lt;/p&gt;
&lt;p&gt;# Arbitrary file write via path traversal in unpackToDir&lt;/p&gt;
&lt;p&gt;`Codec.Archive.unpackToDir` extracts a tar (or other archive supported by the
libarchive C library) from a `ByteString` into a directory. `unpackToDirLazy`
is the streaming variant; both funnel through the same internal
`unpackEntriesFp` routine.&lt;/p&gt;
&lt;p&gt;`unpackEntriesFp` joined each entry&amp;#39;s name onto the destination directory with
`System.FilePath.(&amp;lt;/&amp;gt;)` without validating the name. Entry names starting with
`..` sequences therefore escape the destination: `fp &amp;lt;/&amp;gt; &amp;#34;../../../../etc/x&amp;#34;`
resolves outside the extraction root. The joined path is written back into the
archive entry (`archiveEntrySetPathname`) and handed to libarchive&amp;#39;s
`archive_read_extract` with no `ARCHIVE_EXTRACT_SECURE_*` flags, so neither the
Haskell layer nor the C library rejects the traversal. The `..` check is not
limited to tar archives: any format whose entry names libarchive reports
verbatim is affected. Extraction result codes were also discarded, so write
failures could pass unnoticed.&lt;/p&gt;
&lt;p&gt;An attacker who can supply an archive to a service that extracts it with these
APIs gains an arbitrary file write with the privileges of the extracting
process. A demonstrated escalation (verified in a container): an archive with
member `../../../../etc/profile.d/zz-poc-zipslip.sh` plants a shell script
sourced by every subsequent login shell, converting the file write into code
execution when any user logs in.&lt;/p&gt;
&lt;p&gt;The reported traversal is fixed in libarchive-3.0.6.0,…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/hsec-2026-0014</guid>
      <pubDate>Fri, 13 Nov 2026 11:01:54 +0000</pubDate>
    </item>
    <item>
      <title>HSEC-2026-0013 — HTTP Request Smuggling in warp</title>
      <link>https://vulnerability.circl.lu/vuln/hsec-2026-0013</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: warp&lt;/p&gt;
&lt;p&gt;# HTTP Request Smuggling in warp&lt;/p&gt;
&lt;p&gt;warp&amp;#39;s HTTP/1.x request parser accepted request framing that RFC 9112 requires recipients to refuse, so a request could frame one way for a front-end proxy reading it and another way for warp behind it. Whoever reads such a request the other way sees one request where the other sees two, which smuggles a request past the proxy: past access control, request validation, logging, or WAF rules. warp&amp;#39;s HTTP/2 support delegates parsing to the `http2` package and is not affected.&lt;/p&gt;
&lt;p&gt;Six defects were fixed in warp 3.4.17:&lt;/p&gt;
&lt;p&gt;* `Transfer-Encoding` and `Content-Length` field lines were collapsed to a single value, the last line winning. A second `Content-Length` could hide the first, and a second `Transfer-Encoding` could hide a `chunked` coding.
* Sending `Content-Length` together with `Transfer-Encoding`, or a `Transfer-Encoding` whose final coding is not `chunked`, was not refused; warp resolved the ambiguity by reading whichever framing it recognised.
* `Content-Length` values were parsed by reading the leading digits: a non-numeric value, or one too large for an `Int` which then wrapped, became length 0 — so the request body was read as the next request on the connection.
* Header field names were not validated: an obs-fold continuation line, a name containing whitespace or control characters, or an empty name became a header warp did not act on but a repairing intermediary could, including a hidden `Content-Length`.
* A bare CR or a NUL inside a hea…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: warp&lt;/p&gt;
&lt;p&gt;# HTTP Request Smuggling in warp&lt;/p&gt;
&lt;p&gt;warp&amp;#39;s HTTP/1.x request parser accepted request framing that RFC 9112 requires recipients to refuse, so a request could frame one way for a front-end proxy reading it and another way for warp behind it. Whoever reads such a request the other way sees one request where the other sees two, which smuggles a request past the proxy: past access control, request validation, logging, or WAF rules. warp&amp;#39;s HTTP/2 support delegates parsing to the `http2` package and is not affected.&lt;/p&gt;
&lt;p&gt;Six defects were fixed in warp 3.4.17:&lt;/p&gt;
&lt;p&gt;* `Transfer-Encoding` and `Content-Length` field lines were collapsed to a single value, the last line winning. A second `Content-Length` could hide the first, and a second `Transfer-Encoding` could hide a `chunked` coding.
* Sending `Content-Length` together with `Transfer-Encoding`, or a `Transfer-Encoding` whose final coding is not `chunked`, was not refused; warp resolved the ambiguity by reading whichever framing it recognised.
* `Content-Length` values were parsed by reading the leading digits: a non-numeric value, or one too large for an `Int` which then wrapped, became length 0 — so the request body was read as the next request on the connection.
* Header field names were not validated: an obs-fold continuation line, a name containing whitespace or control characters, or an empty name became a header warp did not act on but a repairing intermediary could, including a hidden `Content-Length`.
* A bare CR or a NUL inside a hea…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/hsec-2026-0013</guid>
      <pubDate>Wed, 04 Nov 2026 12:43:59 +0000</pubDate>
    </item>
    <item>
      <title>HSEC-2026-0012 — Out-of-bounds read in Eq and Ord on numbers with extreme exponents</title>
      <link>https://vulnerability.circl.lu/vuln/hsec-2026-0012</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: scientific&lt;/p&gt;
&lt;p&gt;# Out-of-bounds read in Eq and Ord on numbers with extreme exponents&lt;/p&gt;
&lt;p&gt;`scientific-0.3.9.0` reimplemented `Eq` and `Ord` without normalising their
arguments. The new implementation short-circuits on
`integerLog10&amp;#39; c + e` computed in `Int`, which overflows when the base-10
exponent is close to `maxBound :: Int`. The overflowed comparison then falls
through to `magnitude (e1 - e2)`, where the exponent difference overflows to a
negative `Int` as well. `magnitude` indexed its cached power-of-ten array
without a bounds check, so the negative index performed an out-of-bounds read
and the process died with `SIGSEGV`.&lt;/p&gt;
&lt;p&gt;With `scientific-0.3.9.0` (GHC 9.10.3, x86_64-linux), as reported in
[basvandijk/scientific#120](https://github.com/basvandijk/scientific/issues/120):&lt;/p&gt;
&lt;p&gt;```haskell
import Data.Scientific&lt;/p&gt;
&lt;p&gt;main :: IO ()
main = print (scientific 10 maxBound == scientific 1 minBound)
```&lt;/p&gt;
&lt;p&gt;```
$ ./repro; echo &amp;#34;exit=$?&amp;#34;
exit=139
```&lt;/p&gt;
&lt;p&gt;The issue was discovered when Stackage nightly test suites
(`genvalidity-hspec-aeson`, `genvalidity-sydtest-aeson`) started segfaulting
after upgrading to `scientific-0.3.9.0`: their property tests round-trip
`aeson` `Value`s, which produces `Scientific`s with extreme exponents.&lt;/p&gt;
&lt;p&gt;Versions before `0.3.9.0` did not crash, but `Eq`/`Ord` returned invalid
results there instead (the normalisation-based implementation overflows the
exponent, reporting `scientific 10 maxBound == scientific 1 minBound` as
`True`). The same unchecked read was also reachable through `(+)`…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: scientific&lt;/p&gt;
&lt;p&gt;# Out-of-bounds read in Eq and Ord on numbers with extreme exponents&lt;/p&gt;
&lt;p&gt;`scientific-0.3.9.0` reimplemented `Eq` and `Ord` without normalising their
arguments. The new implementation short-circuits on
`integerLog10&amp;#39; c + e` computed in `Int`, which overflows when the base-10
exponent is close to `maxBound :: Int`. The overflowed comparison then falls
through to `magnitude (e1 - e2)`, where the exponent difference overflows to a
negative `Int` as well. `magnitude` indexed its cached power-of-ten array
without a bounds check, so the negative index performed an out-of-bounds read
and the process died with `SIGSEGV`.&lt;/p&gt;
&lt;p&gt;With `scientific-0.3.9.0` (GHC 9.10.3, x86_64-linux), as reported in
[basvandijk/scientific#120](https://github.com/basvandijk/scientific/issues/120):&lt;/p&gt;
&lt;p&gt;```haskell
import Data.Scientific&lt;/p&gt;
&lt;p&gt;main :: IO ()
main = print (scientific 10 maxBound == scientific 1 minBound)
```&lt;/p&gt;
&lt;p&gt;```
$ ./repro; echo &amp;#34;exit=$?&amp;#34;
exit=139
```&lt;/p&gt;
&lt;p&gt;The issue was discovered when Stackage nightly test suites
(`genvalidity-hspec-aeson`, `genvalidity-sydtest-aeson`) started segfaulting
after upgrading to `scientific-0.3.9.0`: their property tests round-trip
`aeson` `Value`s, which produces `Scientific`s with extreme exponents.&lt;/p&gt;
&lt;p&gt;Versions before `0.3.9.0` did not crash, but `Eq`/`Ord` returned invalid
results there instead (the normalisation-based implementation overflows the
exponent, reporting `scientific 10 maxBound == scientific 1 minBound` as
`True`). The same unchecked read was also reachable through `(+)`…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/hsec-2026-0012</guid>
      <pubDate>Tue, 03 Nov 2026 22:32:58 +0000</pubDate>
    </item>
    <item>
      <title>HSEC-2026-0011 — Superlinear encoding of numbers with large coefficients</title>
      <link>https://vulnerability.circl.lu/vuln/hsec-2026-0011</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: scientific&lt;/p&gt;
&lt;p&gt;# Superlinear encoding of numbers with large coefficients&lt;/p&gt;
&lt;p&gt;Encoding (pretty-printing) a `Scientific` number whose coefficient has many
digits took time quadratic in the number of digits: the decimal digits were
extracted by repeatedly dividing the whole coefficient by 10, once per digit.
The `Show` instance, `Data.Text.Lazy.Builder.Scientific` and
`Data.ByteString.Builder.Scientific` — which `aeson` uses to encode JSON
numbers — all share this code path. A number with one million digits took
about a minute to show, and about a tenth of a second after the fix.&lt;/p&gt;
&lt;p&gt;This is a denial-of-service risk for applications that decode numbers from an
untrusted source and encode them again, e.g. JSON proxies, loggers or API
gateways built on `aeson`.&lt;/p&gt;
&lt;p&gt;## Resolution&lt;/p&gt;
&lt;p&gt;`scientific-0.3.9.0` reimplemented `normalize` and `toDecimalDigits` (the
digit-extraction primitive) to be practically linear in the coefficient size.&lt;/p&gt;
&lt;p&gt;Note that `scientific-0.3.9.0` introduced a regression of its own; see
HSEC-2026-0012. Upgrade
directly to `scientific-0.3.10.0` or later, which fixes both issues.&lt;/p&gt;
&lt;p&gt;## Credits&lt;/p&gt;
&lt;p&gt;Reported by Andrzej Rybczak (@arybczak); fixed by Oleg Grenrus (@phadej).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: scientific&lt;/p&gt;
&lt;p&gt;# Superlinear encoding of numbers with large coefficients&lt;/p&gt;
&lt;p&gt;Encoding (pretty-printing) a `Scientific` number whose coefficient has many
digits took time quadratic in the number of digits: the decimal digits were
extracted by repeatedly dividing the whole coefficient by 10, once per digit.
The `Show` instance, `Data.Text.Lazy.Builder.Scientific` and
`Data.ByteString.Builder.Scientific` — which `aeson` uses to encode JSON
numbers — all share this code path. A number with one million digits took
about a minute to show, and about a tenth of a second after the fix.&lt;/p&gt;
&lt;p&gt;This is a denial-of-service risk for applications that decode numbers from an
untrusted source and encode them again, e.g. JSON proxies, loggers or API
gateways built on `aeson`.&lt;/p&gt;
&lt;p&gt;## Resolution&lt;/p&gt;
&lt;p&gt;`scientific-0.3.9.0` reimplemented `normalize` and `toDecimalDigits` (the
digit-extraction primitive) to be practically linear in the coefficient size.&lt;/p&gt;
&lt;p&gt;Note that `scientific-0.3.9.0` introduced a regression of its own; see
HSEC-2026-0012. Upgrade
directly to `scientific-0.3.10.0` or later, which fixes both issues.&lt;/p&gt;
&lt;p&gt;## Credits&lt;/p&gt;
&lt;p&gt;Reported by Andrzej Rybczak (@arybczak); fixed by Oleg Grenrus (@phadej).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/hsec-2026-0011</guid>
      <pubDate>Tue, 03 Nov 2026 22:32:58 +0000</pubDate>
    </item>
    <item>
      <title>HSEC-2026-0010 — Improper parsing of fractional NumericDate from JWT exp claims</title>
      <link>https://vulnerability.circl.lu/vuln/hsec-2026-0010</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: jwt&lt;/p&gt;
&lt;p&gt;# Improper parsing of fractional `NumericDate` from JWT `exp` claims&lt;/p&gt;
&lt;p&gt;Since its [initial commit][], package jwt uses [`Data.Scientific.coefficient`][scientific] to extract the fractional mantissa in a way that improperly *discards the exponent*. This can lead to incorrect parsing of the `exp` claim in JWT payload body.&lt;/p&gt;
&lt;p&gt;PoC:&lt;/p&gt;
&lt;p&gt;```haskell
cabal repl --build-depends jwt==0.11.0&lt;/p&gt;
&lt;p&gt;import Web.JWT
:set -XOverloadedStrings&lt;/p&gt;
&lt;p&gt;let signer = VerifyHMACSecret &amp;#34;dummy-signing-symmetric-hmac-key.not-so-secret&amp;#34;
let exploit = &amp;#34;eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkhvbmVzdCBKb2UiLCJhZG1pbiI6dHJ1ZSwiaWF0IjoxNzkwMTY2Nzg2LCJleHAiOjE3OTAxNzAzODYuMDAwMX0.xQyl3rBYtVTxPL_VXSawSSmZkuF4MzOkzwdQGJFjE2o&amp;#34;
-- {
--   &amp;#34;sub&amp;#34;: &amp;#34;1234567890&amp;#34;,
--   &amp;#34;name&amp;#34;: &amp;#34;Honest Joe&amp;#34;,
--   &amp;#34;admin&amp;#34;: true,
--   &amp;#34;iat&amp;#34;: 1790166786,
--   &amp;#34;exp&amp;#34;: 1790170386.0001
-- }
λλ ➔ Just whoops = Web.JWT.decodeAndVerifySignature signer exploit
λ
λλ ➔ whoops
Verified (JOSEHeader {typ = Just &amp;#34;JWT&amp;#34;, cty = Nothing, alg = Just HS256, kid = Nothing}) (JWTClaimsSet {iss = Nothing, sub = Just 1234567890, aud = Nothing, exp = Just (NumericDate 17901703860001), nbf = Nothing, iat = Just (NumericDate 1790166786), jti = Nothing, unregisteredClaims = ClaimsMap {unClaimsMap = fromList [(&amp;#34;admin&amp;#34;,Bool True),(&amp;#34;name&amp;#34;,String &amp;#34;Honest Joe&amp;#34;)]}}) (Signature &amp;#34;xQyl3rBYtVTxPL_VXSawSSmZkuF4MzOkzwdQGJFjE2o&amp;#34;)
λ
λλ ➔ fmap secondsSinceEpoch . Web.JWT.iat . claims $ whoops
Just 1790166786s
λ
λλ ➔ fmap secondsSinceEpoch . Web.JWT.exp . claims…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: jwt&lt;/p&gt;
&lt;p&gt;# Improper parsing of fractional `NumericDate` from JWT `exp` claims&lt;/p&gt;
&lt;p&gt;Since its [initial commit][], package jwt uses [`Data.Scientific.coefficient`][scientific] to extract the fractional mantissa in a way that improperly *discards the exponent*. This can lead to incorrect parsing of the `exp` claim in JWT payload body.&lt;/p&gt;
&lt;p&gt;PoC:&lt;/p&gt;
&lt;p&gt;```haskell
cabal repl --build-depends jwt==0.11.0&lt;/p&gt;
&lt;p&gt;import Web.JWT
:set -XOverloadedStrings&lt;/p&gt;
&lt;p&gt;let signer = VerifyHMACSecret &amp;#34;dummy-signing-symmetric-hmac-key.not-so-secret&amp;#34;
let exploit = &amp;#34;eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkhvbmVzdCBKb2UiLCJhZG1pbiI6dHJ1ZSwiaWF0IjoxNzkwMTY2Nzg2LCJleHAiOjE3OTAxNzAzODYuMDAwMX0.xQyl3rBYtVTxPL_VXSawSSmZkuF4MzOkzwdQGJFjE2o&amp;#34;
-- {
--   &amp;#34;sub&amp;#34;: &amp;#34;1234567890&amp;#34;,
--   &amp;#34;name&amp;#34;: &amp;#34;Honest Joe&amp;#34;,
--   &amp;#34;admin&amp;#34;: true,
--   &amp;#34;iat&amp;#34;: 1790166786,
--   &amp;#34;exp&amp;#34;: 1790170386.0001
-- }
λλ ➔ Just whoops = Web.JWT.decodeAndVerifySignature signer exploit
λ
λλ ➔ whoops
Verified (JOSEHeader {typ = Just &amp;#34;JWT&amp;#34;, cty = Nothing, alg = Just HS256, kid = Nothing}) (JWTClaimsSet {iss = Nothing, sub = Just 1234567890, aud = Nothing, exp = Just (NumericDate 17901703860001), nbf = Nothing, iat = Just (NumericDate 1790166786), jti = Nothing, unregisteredClaims = ClaimsMap {unClaimsMap = fromList [(&amp;#34;admin&amp;#34;,Bool True),(&amp;#34;name&amp;#34;,String &amp;#34;Honest Joe&amp;#34;)]}}) (Signature &amp;#34;xQyl3rBYtVTxPL_VXSawSSmZkuF4MzOkzwdQGJFjE2o&amp;#34;)
λ
λλ ➔ fmap secondsSinceEpoch . Web.JWT.iat . claims $ whoops
Just 1790166786s
λ
λλ ➔ fmap secondsSinceEpoch . Web.JWT.exp . claims…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/hsec-2026-0010</guid>
      <pubDate>Tue, 29 Sep 2026 14:22:37 +0000</pubDate>
    </item>
    <item>
      <title>HSEC-2026-0008 — crypton-x509-validation and crypton-x509 do not enforce X.509 Name Constraints</title>
      <link>https://vulnerability.circl.lu/vuln/hsec-2026-0008</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: crypton-x509-validation, Hackage: crypton-x509, Hackage: x509-validation, Hackage: x509&lt;/p&gt;
&lt;p&gt;# crypton-x509-validation and crypton-x509 do not enforce X.509 Name Constraints&lt;/p&gt;
&lt;p&gt;The `crypton-x509-validation` and `crypton-x509` libraries did not
enforce the X.509 Name Constraints extension during certificate
validation. The Name Constraints extension is a critical X.509
extension that restricts the namespace (permitted and excluded
subtrees) for which a CA is authorized to issue certificates.&lt;/p&gt;
&lt;p&gt;Without this enforcement, a TLS client would accept certificates with
Subject Alternative Names (SANs) that fall outside the issuing CA&amp;#39;s
permitted subtrees. An attacker with access to a name-constrained
sub-CA&amp;#39;s private key could therefore issue certificates for domains
outside the sub-CA&amp;#39;s intended scope, enabling impersonation of
arbitrary domains and man-in-the-middle attacks on TLS connections.&lt;/p&gt;
&lt;p&gt;The older `x509` and `x509-validation` packages are also affected but
are no longer maintained and have no fix available.&lt;/p&gt;
&lt;p&gt;This issue was fixed in `crypton-x509-validation-1.9.1` and
`crypton-x509-1.9.1`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: crypton-x509-validation, Hackage: crypton-x509, Hackage: x509-validation, Hackage: x509&lt;/p&gt;
&lt;p&gt;# crypton-x509-validation and crypton-x509 do not enforce X.509 Name Constraints&lt;/p&gt;
&lt;p&gt;The `crypton-x509-validation` and `crypton-x509` libraries did not
enforce the X.509 Name Constraints extension during certificate
validation. The Name Constraints extension is a critical X.509
extension that restricts the namespace (permitted and excluded
subtrees) for which a CA is authorized to issue certificates.&lt;/p&gt;
&lt;p&gt;Without this enforcement, a TLS client would accept certificates with
Subject Alternative Names (SANs) that fall outside the issuing CA&amp;#39;s
permitted subtrees. An attacker with access to a name-constrained
sub-CA&amp;#39;s private key could therefore issue certificates for domains
outside the sub-CA&amp;#39;s intended scope, enabling impersonation of
arbitrary domains and man-in-the-middle attacks on TLS connections.&lt;/p&gt;
&lt;p&gt;The older `x509` and `x509-validation` packages are also affected but
are no longer maintained and have no fix available.&lt;/p&gt;
&lt;p&gt;This issue was fixed in `crypton-x509-validation-1.9.1` and
`crypton-x509-1.9.1`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/hsec-2026-0008</guid>
      <pubDate>Wed, 03 Jun 2026 13:30:48 +0000</pubDate>
    </item>
    <item>
      <title>HSEC-2026-0007 — Denial of Service and Memory Exhaustion in aeson</title>
      <link>https://vulnerability.circl.lu/vuln/hsec-2026-0007</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: aeson, Hackage: text-iso8601&lt;/p&gt;
&lt;p&gt;# Denial of Service and Memory Exhaustion in aeson&lt;/p&gt;
&lt;p&gt;A Denial of Service (DoS) and memory exhaustion vulnerability was identified in the `aeson` package. The vulnerability allows an attacker to exhaust server memory and crash the host process by supplying maliciously crafted JSON payloads.&lt;/p&gt;
&lt;p&gt;The vulnerability exists in `aeson`&amp;#39;s `withBoundedScientific_` function (located in `src/Data/Aeson/Types/FromJSON.hs`). The exponent bounds check only rejects large positive exponents (`exp10 &amp;gt; 1024`) but fails to reject arbitrarily large negative exponents.&lt;/p&gt;
&lt;p&gt;When an attacker sends a JSON number with a massive negative exponent (e.g., `1e-999999999`), the value bypasses the check and flows into `realToFrac`, which computes `fromRational . toRational`. For such a large negative exponent, `toRational` produces a GMP Integer with approximately 1 billion decimal digits, causing immediate and severe memory exhaustion.&lt;/p&gt;
&lt;p&gt;Affected `FromJSON` instances:&lt;/p&gt;
&lt;p&gt;* `Fixed a` (including `Centi`, `Pico`, `Nano`, etc.)
* `NominalDiffTime`
* `DiffTime`&lt;/p&gt;
&lt;p&gt;## Resolution&lt;/p&gt;
&lt;p&gt;The issue was resolved by introducing proper bounds checks:&lt;/p&gt;
&lt;p&gt;- `aeson` now applies an absolute bounds check to both positive and negative exponents (`abs exp10 &amp;gt; 1024`).&lt;/p&gt;
&lt;p&gt;The fix first shipped in `aeson-2.3.0.0`, and have been backported to the previous release series as `aeson-2.2.5.1`.&lt;/p&gt;
&lt;p&gt;Users are strongly advised to update to the patched versions:&lt;/p&gt;
&lt;p&gt;* `aeson-2.2.5.1` or later&lt;/p&gt;
&lt;p&gt;## Acknowledgements&lt;/p&gt;
&lt;p&gt;The vulnerabilities were reported Nathan Walsh,…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: aeson, Hackage: text-iso8601&lt;/p&gt;
&lt;p&gt;# Denial of Service and Memory Exhaustion in aeson&lt;/p&gt;
&lt;p&gt;A Denial of Service (DoS) and memory exhaustion vulnerability was identified in the `aeson` package. The vulnerability allows an attacker to exhaust server memory and crash the host process by supplying maliciously crafted JSON payloads.&lt;/p&gt;
&lt;p&gt;The vulnerability exists in `aeson`&amp;#39;s `withBoundedScientific_` function (located in `src/Data/Aeson/Types/FromJSON.hs`). The exponent bounds check only rejects large positive exponents (`exp10 &amp;gt; 1024`) but fails to reject arbitrarily large negative exponents.&lt;/p&gt;
&lt;p&gt;When an attacker sends a JSON number with a massive negative exponent (e.g., `1e-999999999`), the value bypasses the check and flows into `realToFrac`, which computes `fromRational . toRational`. For such a large negative exponent, `toRational` produces a GMP Integer with approximately 1 billion decimal digits, causing immediate and severe memory exhaustion.&lt;/p&gt;
&lt;p&gt;Affected `FromJSON` instances:&lt;/p&gt;
&lt;p&gt;* `Fixed a` (including `Centi`, `Pico`, `Nano`, etc.)
* `NominalDiffTime`
* `DiffTime`&lt;/p&gt;
&lt;p&gt;## Resolution&lt;/p&gt;
&lt;p&gt;The issue was resolved by introducing proper bounds checks:&lt;/p&gt;
&lt;p&gt;- `aeson` now applies an absolute bounds check to both positive and negative exponents (`abs exp10 &amp;gt; 1024`).&lt;/p&gt;
&lt;p&gt;The fix first shipped in `aeson-2.3.0.0`, and have been backported to the previous release series as `aeson-2.2.5.1`.&lt;/p&gt;
&lt;p&gt;Users are strongly advised to update to the patched versions:&lt;/p&gt;
&lt;p&gt;* `aeson-2.2.5.1` or later&lt;/p&gt;
&lt;p&gt;## Acknowledgements&lt;/p&gt;
&lt;p&gt;The vulnerabilities were reported Nathan Walsh,…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/hsec-2026-0007</guid>
      <pubDate>Fri, 22 May 2026 07:02:58 +0000</pubDate>
    </item>
  </channel>
</rss>
