<?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_julia</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:22:59 +0000</lastBuildDate>
    <item>
      <title>JLSEC-2026-1263</title>
      <link>https://vulnerability.circl.lu/vuln/jlsec-2026-1263</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: Libmount_jll, Julia: util_linux_jll&lt;/p&gt;
&lt;p&gt;A flaw was found in the libblkid library of util-linux. During nested partition probing, the BSD, Minix, Solaris x86, and UnixWare partition probers cache a raw pointer to a parent partition entry in a dynamically allocated array. When subsequent partition additions cause the array to be reallocated, this pointer becomes stale, leading to a heap use-after-free read. An attacker who can present a crafted block device image (for example, via USB insertion or a loop-mounted disk image) can trigger this flaw without user interaction, as libblkid is invoked automatically by udev/udisks as root on block-device hot-plug events. This could lead to limited information disclosure or denial of service.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: Libmount_jll, Julia: util_linux_jll&lt;/p&gt;
&lt;p&gt;A flaw was found in the libblkid library of util-linux. During nested partition probing, the BSD, Minix, Solaris x86, and UnixWare partition probers cache a raw pointer to a parent partition entry in a dynamically allocated array. When subsequent partition additions cause the array to be reallocated, this pointer becomes stale, leading to a heap use-after-free read. An attacker who can present a crafted block device image (for example, via USB insertion or a loop-mounted disk image) can trigger this flaw without user interaction, as libblkid is invoked automatically by udev/udisks as root on block-device hot-plug events. This could lead to limited information disclosure or denial of service.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/jlsec-2026-1263</guid>
      <pubDate>Wed, 12 Aug 2026 15:58:36 +0000</pubDate>
    </item>
    <item>
      <title>JLSEC-2026-1169 — 7-Zip for Windows fails to preserve the Mark-of-the-Web when extracting a crafted RAR5 archive</title>
      <link>https://vulnerability.circl.lu/vuln/jlsec-2026-1169</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: p7zip_jll&lt;/p&gt;
&lt;p&gt;7-Zip for Windows through 26.02 fails to preserve the Mark-of-the-Web when extracting a crafted RAR5 archive, because its guard that suppresses an archive-supplied Zone.Identifier stream matches the exact name &amp;#39;Zone.Identifier&amp;#39; while a RAR5 STM record named &amp;#39;:Zone.Identifier:$DATA&amp;#39; is not matched and NTFS canonicalizes it to the same stream, overwriting the propagated Internet-zone marker with ZoneId=0. A second STM record named &amp;#39;::$DATA&amp;#39; overwrites the extracted file&amp;#39;s default data stream, letting an attacker defeat SmartScreen/MotW warnings and spoof file content.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: p7zip_jll&lt;/p&gt;
&lt;p&gt;7-Zip for Windows through 26.02 fails to preserve the Mark-of-the-Web when extracting a crafted RAR5 archive, because its guard that suppresses an archive-supplied Zone.Identifier stream matches the exact name &amp;#39;Zone.Identifier&amp;#39; while a RAR5 STM record named &amp;#39;:Zone.Identifier:$DATA&amp;#39; is not matched and NTFS canonicalizes it to the same stream, overwriting the propagated Internet-zone marker with ZoneId=0. A second STM record named &amp;#39;::$DATA&amp;#39; overwrites the extracted file&amp;#39;s default data stream, letting an attacker defeat SmartScreen/MotW warnings and spoof file content.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/jlsec-2026-1169</guid>
      <pubDate>Wed, 05 Aug 2026 21:11:23 +0000</pubDate>
    </item>
    <item>
      <title>JLSEC-2026-1389 — Heap buffer overflow when `read_command` on a collection fails in Mongoc.jl</title>
      <link>https://vulnerability.circl.lu/vuln/jlsec-2026-1389</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: Mongoc&lt;/p&gt;
&lt;p&gt;### Description&lt;/p&gt;
&lt;p&gt;`Mongoc.read_command(collection, command)` called the wrong libmongoc function. Its binding for
`mongoc_collection_read_command_with_opts` called `mongoc_collection_command_simple`, which takes one
argument fewer, so libmongoc read every argument after `read_prefs` one place early. libmongoc wrote
its `bson_error_t` into the reply document, wrote the reply into the caller&amp;#39;s `options` document (or
discarded it when no options were given), and never filled in the error that Mongoc.jl reads, so
the exception thrown for a failure carried no error code or message.&lt;/p&gt;
&lt;p&gt;The reply document is a 128-byte `bson_t` that `bson_new` allocates on the C heap. A `bson_error_t`
is 512 bytes. When the command fails, libmongoc writes to the last byte of the error, 384 bytes past
the end of the allocation. A message longer than about 120 bytes also writes its text past the end.
The message comes from the MongoDB server or from libmongoc, and server messages can echo parts of
the command: the error for an unknown query operator includes the operator&amp;#39;s name.&lt;/p&gt;
&lt;p&gt;Calls that succeeded returned an empty document instead of the reply. A call with `options`
overwrote the caller&amp;#39;s options document with the reply.&lt;/p&gt;
&lt;p&gt;Only `read_command(collection, ...)` is affected. A comparison of all of the package&amp;#39;s `ccall`s with
the libmongoc headers found no other wrong function or argument count.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Each failing `read_command(collection, ...)` call corrupts the C heap of the Julia process. This…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: Mongoc&lt;/p&gt;
&lt;p&gt;### Description&lt;/p&gt;
&lt;p&gt;`Mongoc.read_command(collection, command)` called the wrong libmongoc function. Its binding for
`mongoc_collection_read_command_with_opts` called `mongoc_collection_command_simple`, which takes one
argument fewer, so libmongoc read every argument after `read_prefs` one place early. libmongoc wrote
its `bson_error_t` into the reply document, wrote the reply into the caller&amp;#39;s `options` document (or
discarded it when no options were given), and never filled in the error that Mongoc.jl reads, so
the exception thrown for a failure carried no error code or message.&lt;/p&gt;
&lt;p&gt;The reply document is a 128-byte `bson_t` that `bson_new` allocates on the C heap. A `bson_error_t`
is 512 bytes. When the command fails, libmongoc writes to the last byte of the error, 384 bytes past
the end of the allocation. A message longer than about 120 bytes also writes its text past the end.
The message comes from the MongoDB server or from libmongoc, and server messages can echo parts of
the command: the error for an unknown query operator includes the operator&amp;#39;s name.&lt;/p&gt;
&lt;p&gt;Calls that succeeded returned an empty document instead of the reply. A call with `options`
overwrote the caller&amp;#39;s options document with the reply.&lt;/p&gt;
&lt;p&gt;Only `read_command(collection, ...)` is affected. A comparison of all of the package&amp;#39;s `ccall`s with
the libmongoc headers found no other wrong function or argument count.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Each failing `read_command(collection, ...)` call corrupts the C heap of the Julia process. This…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/jlsec-2026-1389</guid>
      <pubDate>Thu, 19 Nov 2026 22:47:03 +0000</pubDate>
    </item>
    <item>
      <title>JLSEC-2026-1388 — Printing a `TLS.Config` exposes TLS session secrets in Reseau.jl</title>
      <link>https://vulnerability.circl.lu/vuln/jlsec-2026-1388</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: Reseau&lt;/p&gt;
&lt;p&gt;### Description&lt;/p&gt;
&lt;p&gt;`Reseau.TLS.Config` keeps the server&amp;#39;s session-ticket keys and the client&amp;#39;s cached TLS sessions in private fields.
These fields arrived with Reseau&amp;#39;s native TLS stack in 1.1.0. Before 1.7.0, `Config` had no `show` method that left
them out, so `show`, `print`, `repr`, `string` and string interpolation of a config that had handled connections
printed the ticket keys&amp;#39; secret bytes and the cached sessions&amp;#39; secrets.&lt;/p&gt;
&lt;p&gt;Reseau 1.7.0 prints only a config&amp;#39;s public settings, and masks `key_passphrase`. `Base.dump` still prints every
field of any value.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An application that prints or logs a `TLS.Config` after it has handled connections writes these secrets to that
output. Anyone who can read the output can:&lt;/p&gt;
&lt;p&gt;- Decrypt the session tickets that a server issued while the printed ticket keys were in use. A TLS 1.2 ticket carries
    the session&amp;#39;s master secret, which decrypts recorded traffic of that session and of its resumptions. A TLS 1.3
    ticket carries a resumption key that lets them resume the session as the client.
  - Use a client&amp;#39;s cached TLS 1.2 session secrets to decrypt recorded traffic of those sessions, and its TLS 1.3
    resumption keys to resume those sessions as the client.&lt;/p&gt;
&lt;p&gt;Reseau resumes TLS 1.3 sessions only with a new key exchange (`psk_dhe_ke`), so a TLS 1.3 secret does not decrypt
recorded traffic. Session tickets are on by default.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in Reseau 1.7.0. Upgrade to 1.7.0 or later.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Don&amp;#39;t print or log…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: Reseau&lt;/p&gt;
&lt;p&gt;### Description&lt;/p&gt;
&lt;p&gt;`Reseau.TLS.Config` keeps the server&amp;#39;s session-ticket keys and the client&amp;#39;s cached TLS sessions in private fields.
These fields arrived with Reseau&amp;#39;s native TLS stack in 1.1.0. Before 1.7.0, `Config` had no `show` method that left
them out, so `show`, `print`, `repr`, `string` and string interpolation of a config that had handled connections
printed the ticket keys&amp;#39; secret bytes and the cached sessions&amp;#39; secrets.&lt;/p&gt;
&lt;p&gt;Reseau 1.7.0 prints only a config&amp;#39;s public settings, and masks `key_passphrase`. `Base.dump` still prints every
field of any value.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An application that prints or logs a `TLS.Config` after it has handled connections writes these secrets to that
output. Anyone who can read the output can:&lt;/p&gt;
&lt;p&gt;- Decrypt the session tickets that a server issued while the printed ticket keys were in use. A TLS 1.2 ticket carries
    the session&amp;#39;s master secret, which decrypts recorded traffic of that session and of its resumptions. A TLS 1.3
    ticket carries a resumption key that lets them resume the session as the client.
  - Use a client&amp;#39;s cached TLS 1.2 session secrets to decrypt recorded traffic of those sessions, and its TLS 1.3
    resumption keys to resume those sessions as the client.&lt;/p&gt;
&lt;p&gt;Reseau resumes TLS 1.3 sessions only with a new key exchange (`psk_dhe_ke`), so a TLS 1.3 secret does not decrypt
recorded traffic. Session tickets are on by default.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in Reseau 1.7.0. Upgrade to 1.7.0 or later.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Don&amp;#39;t print or log…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/jlsec-2026-1388</guid>
      <pubDate>Mon, 16 Nov 2026 13:05:52 +0000</pubDate>
    </item>
    <item>
      <title>JLSEC-2026-1387 — A cross-site scripting vulnerability in queryparser/termgenerator_internal.cc in Xapian xapian...</title>
      <link>https://vulnerability.circl.lu/vuln/jlsec-2026-1387</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: xapian_jll&lt;/p&gt;
&lt;p&gt;A cross-site scripting vulnerability in
`queryparser/termgenerator_internal.cc` in Xapian xapian-core before 2.1.0 and before 1.4.32 exists due to incomplete HTML escaping by Xapian::MSet::snippet(). NOTE: this issue exists because of a missed corner case of CVE-2018-0499.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: xapian_jll&lt;/p&gt;
&lt;p&gt;A cross-site scripting vulnerability in
`queryparser/termgenerator_internal.cc` in Xapian xapian-core before 2.1.0 and before 1.4.32 exists due to incomplete HTML escaping by Xapian::MSet::snippet(). NOTE: this issue exists because of a missed corner case of CVE-2018-0499.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/jlsec-2026-1387</guid>
      <pubDate>Mon, 24 Aug 2026 18:22:23 +0000</pubDate>
    </item>
    <item>
      <title>JLSEC-2026-1386</title>
      <link>https://vulnerability.circl.lu/vuln/jlsec-2026-1386</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: HDF5_jll&lt;/p&gt;
&lt;p&gt;HDF5 contains a NULL pointer dereference vulnerability. Processing a crafted HDF5 file containing an attribute with an invalid variable-length datatype type field may cause the application to crash when the attribute is read.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: HDF5_jll&lt;/p&gt;
&lt;p&gt;HDF5 contains a NULL pointer dereference vulnerability. Processing a crafted HDF5 file containing an attribute with an invalid variable-length datatype type field may cause the application to crash when the attribute is read.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/jlsec-2026-1386</guid>
      <pubDate>Mon, 24 Aug 2026 14:19:02 +0000</pubDate>
    </item>
    <item>
      <title>JLSEC-2026-1385</title>
      <link>https://vulnerability.circl.lu/vuln/jlsec-2026-1385</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: HDF5_jll&lt;/p&gt;
&lt;p&gt;A double free vulnerability was discovered in the HDF5 library. Processing a crafted HDF5 file containing an oversized chunk size field via h5repack may cause the application to abort due to a double free.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: HDF5_jll&lt;/p&gt;
&lt;p&gt;A double free vulnerability was discovered in the HDF5 library. Processing a crafted HDF5 file containing an oversized chunk size field via h5repack may cause the application to abort due to a double free.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/jlsec-2026-1385</guid>
      <pubDate>Mon, 24 Aug 2026 14:19:02 +0000</pubDate>
    </item>
    <item>
      <title>JLSEC-2026-1384</title>
      <link>https://vulnerability.circl.lu/vuln/jlsec-2026-1384</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: HDF5_jll&lt;/p&gt;
&lt;p&gt;Heap-based buffer overflow in the SOHM list-index deserialization code in HDF5 through 2.1.1 on all platforms allows attackers to cause a denial of service (crash) via a crafted HDF5 file whose shared-message list index declares a `num_messages` count exceeding `list_max`, triggering out-of-bounds heap reads and writes in `H5SM__cache_list_deserialize` and `H5SM__cache_list_verify_chksum`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: HDF5_jll&lt;/p&gt;
&lt;p&gt;Heap-based buffer overflow in the SOHM list-index deserialization code in HDF5 through 2.1.1 on all platforms allows attackers to cause a denial of service (crash) via a crafted HDF5 file whose shared-message list index declares a `num_messages` count exceeding `list_max`, triggering out-of-bounds heap reads and writes in `H5SM__cache_list_deserialize` and `H5SM__cache_list_verify_chksum`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/jlsec-2026-1384</guid>
      <pubDate>Mon, 24 Aug 2026 14:19:02 +0000</pubDate>
    </item>
    <item>
      <title>JLSEC-2026-1383</title>
      <link>https://vulnerability.circl.lu/vuln/jlsec-2026-1383</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: Mongoose_jll&lt;/p&gt;
&lt;p&gt;Mongoose is an embedded web server and network library. Prior to 7.22, a remote attacker can send a crafted percent-encoded request path to a deployment using `MG_ENABLE_DIRLIST` and persuade a user to visit it. The `mg_http_serve_dir()` and listdir() path in `src/http.c` places the decoded request URI into the title and h1 elements without HTML entity encoding. The resulting reflected cross-site scripting executes in the Mongoose origin and can expose session data or perform actions as the victim. This issue is fixed in version 7.22.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: Mongoose_jll&lt;/p&gt;
&lt;p&gt;Mongoose is an embedded web server and network library. Prior to 7.22, a remote attacker can send a crafted percent-encoded request path to a deployment using `MG_ENABLE_DIRLIST` and persuade a user to visit it. The `mg_http_serve_dir()` and listdir() path in `src/http.c` places the decoded request URI into the title and h1 elements without HTML entity encoding. The resulting reflected cross-site scripting executes in the Mongoose origin and can expose session data or perform actions as the victim. This issue is fixed in version 7.22.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/jlsec-2026-1383</guid>
      <pubDate>Mon, 24 Aug 2026 13:43:17 +0000</pubDate>
    </item>
    <item>
      <title>JLSEC-2026-1382</title>
      <link>https://vulnerability.circl.lu/vuln/jlsec-2026-1382</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: Mongoose_jll&lt;/p&gt;
&lt;p&gt;Mongoose is an embedded web server and network library. Prior to 7.22, a remote attacker can place a lone carriage return or line feed in multipart input processed by `mg_http_next_multipart()` in `src/http.c`. The loops comparing s[b] and s[b + 1], and s[h2] and s[h2 + 1], use an incorrect AND condition and stop when either character resembles part of a CRLF terminator. This truncates headers, filenames, or boundaries and can cause an application to accept dangerous content after seeing a misleading Content-Type value. This issue is fixed in version 7.22.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Julia: Mongoose_jll&lt;/p&gt;
&lt;p&gt;Mongoose is an embedded web server and network library. Prior to 7.22, a remote attacker can place a lone carriage return or line feed in multipart input processed by `mg_http_next_multipart()` in `src/http.c`. The loops comparing s[b] and s[b + 1], and s[h2] and s[h2 + 1], use an incorrect AND condition and stop when either character resembles part of a CRLF terminator. This truncates headers, filenames, or boundaries and can cause an application to accept dangerous content after seeing a misleading Content-Type value. This issue is fixed in version 7.22.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/jlsec-2026-1382</guid>
      <pubDate>Mon, 24 Aug 2026 13:43:17 +0000</pubDate>
    </item>
  </channel>
</rss>
