<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-01T13:50:50.176484+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-119279</id>
    <title>fkie_cve-2026-119279</title>
    <updated>2026-11-01T13:50:50.207336+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. From 3.0.0 until 3.3.7, 3.4.5, and 3.5.10, the ReadableByteBuf.readLength() and ReadableByteBuf.readIntLengthEncodedNotNull() methods narrowed the protocol's unsigned 8-byte length-encoded integer to a Java int without checking that the value fit a non-negative integer. Values above Integer.MAX_VALUE could wrap to a negative or unrelated length that downstream allocation and read paths used. A malicious or compromised server, or a machine-in-the-middle attacker, could trigger NegativeArraySizeException, out-of-bounds failures, or oversized allocation behavior in client connection handling. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.10.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-119279"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-797x-p4mc-jwpm</id>
    <title>GHSA-797x-p4mc-jwpm — MariaDB Connector/J: Length-encoded integers larger than Integer.MAX_VALUE were truncated before being used as lengths</title>
    <updated>2026-11-01T13:50:50.207410+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: org.mariadb.jdbc:mariadb-java-client</p>
<p>## Summary</p>
<p>MariaDB Connector/J narrowed 8-byte length-encoded integers received from the
server to `int` without validation. A rogue or MitM server can send a value above
`Integer.MAX_VALUE` whose truncation becomes a negative or arbitrary length.</p>
<p>## Details</p>
<p>The protocol encodes lengths as length-encoded integers, whose 8-byte form the
decoder (`readLength()` and `readIntLengthEncodedNotNull()`) returned as
`(int) readLong()`. A value above `Integer.MAX_VALUE` therefore wrapped to a
negative or unrelated `int`, used afterwards as a length to size allocations or
reads, which ended in `NegativeArraySizeException`, out-of-bounds exceptions or
oversized allocations.</p>
<p>The fix rejects any length-encoded value that does not fit a non-negative `int`
with an explicit error.</p>
<p>## Impact</p>
<p>Availability only: a malicious or compromised server, or a MitM, can crash the
client's connection handling with unchecked exceptions or drive oversized
allocations. Exploitation requires control of the server side of the connection;
no authentication bypass, confidentiality or integrity impact.</p>
<p>## Credit</p>
<p>Reported by fg0x0</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-797x-p4mc-jwpm"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ubuntu-cve-2026-119279</id>
    <title>UBUNTU-CVE-2026-119279</title>
    <updated>2026-11-01T13:50:50.207457+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:18.04:LTS: mariadb-connector-java, Ubuntu:20.04:LTS: mariadb-connector-java, Ubuntu:22.04:LTS: mariadb-connector-java, Ubuntu:24.04:LTS: mariadb-connector-java, Ubuntu:26.10: mariadb-connector-java, Ubuntu:26.04:LTS: mariadb-connector-java</p>
<p>MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. From 3.0.0 until 3.3.7, 3.4.5, and 3.5.10, the ReadableByteBuf.readLength() and ReadableByteBuf.readIntLengthEncodedNotNull() methods narrowed the protocol's unsigned 8-byte length-encoded integer to a Java int without checking that the value fit a non-negative integer. Values above Integer.MAX_VALUE could wrap to a negative or unrelated length that downstream allocation and read paths used. A malicious or compromised server, or a machine-in-the-middle attacker, could trigger NegativeArraySizeException, out-of-bounds failures, or oversized allocation behavior in client connection handling. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.10.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ubuntu-cve-2026-119279"/>
  </entry>
</feed>
