CVE
CVE-2026-123614, CVE-2026-123615, CVE-2026-123616, CVE-2026-119210, CVE-2026-119276, CVE-2026-119279, CVE-2026-119280, CVE-2026-119281, CVE-2026-116794, CVE-2026-116773, CVE-2026-116774, CVE-2026-116696, CVE-2026-116775, CVE-2026-111062, CVE-2026-102823, CVE-2026-48110, CVE-2026-46702, CVE-2026-42189, CVE-2024-43410, CVE-2026-118669, CVE-2026-49272, CVE-2026-116689, CVE-2026-120135, CVE-2026-118636, CVE-2026-43868
CWE
CWE-190, CWE-787, CWE-73, CWE-287, CWE-863, CWE-200, CWE-674, CWE-502, CWE-400
Affected Surface
- Go / C `imgproxy` (`github.com/imgproxy/imgproxy/v3`) versions `>= 3.3.0, < 4.0.17` (`GHSA-hff9-5pqw-6w9f` Critical integer overflow in `vips/icoload.c`, `GHSA-mmq5-xm89-9pfg` High 4 GB `VIPS_MALLOC` DoS, and `GHSA-494m-4556-wf5p` High out-of-bounds heap write in BMP header reconstruction)
- Maven `org.mariadb.jdbc:mariadb-java-client` versions `>= 3.0.0, < 3.3.7`, `>= 3.4.0, < 3.4.5`, and `>= 3.5.0, < 3.5.11` (`CVE-2026-119210` / `GHSA-fhx5-2xqw-2cgm`, `CVE-2026-119276` / `GHSA-h599-m3w5-9m7x`, `CVE-2026-119279` / `GHSA-797x-p4mc-jwpm`, `CVE-2026-119280`, and `CVE-2026-119281`), plus MariaDB Server `>= 10.11.1` before `10.11.19`, `11.4.13`, `11.8.9`, `12.3.3`, and `13.0.2` (`CVE-2026-102523`, CVSS 8.0 High)
- crates.io `russh` versions `< 0.65.0` (`RUSTSEC-2026-0495` / `CVE-2026-116794`, `RUSTSEC-2026-0492` / `CVE-2026-102823` `< 0.63.1`, `RUSTSEC-2026-0493` / `CVE-2026-46702` `< 0.61.1`, `RUSTSEC-2026-0494` / `CVE-2026-48110` `< 0.61.0`, `RUSTSEC-2026-0496` / `CVE-2026-42189` `< 0.60.1`, `RUSTSEC-2024-0450` / `CVE-2024-43410` `< 0.44.1`, `CVE-2026-111062` `< 0.64.0`, `CVE-2026-116773`, `CVE-2026-116774`, and `CVE-2026-116696`), `pageant` `>= 0.2.0, < 0.2.5` (`CVE-2026-116775`), `bsv-rs` `< 0.8.7` and `0.9.0-beta.1`..`0.9.0-beta.7` (`RUSTSEC-2026-0497` to `0501`), and `eazip` `>= 0.2.5, < 0.2.7` (`RUSTSEC-2026-0503`)
- PyPI `oauthlib` versions `>= 3.3.0, < 4.0.1` (`CVE-2026-49272` / `GHSA-3jp2-3mrg-2vxc` CVSS 8.5 High, fixed in `4.0.1`) and `< 4.0.0` (`CVE-2026-118669` / `GHSA-7984-qgvg-3j9c` High)
- npm `follow-redirects` versions `1.16.0` and `1.16.1` (`CVE-2026-116689` / `GHSA-mrwp-f3q8-3g9p` High)
- Maven `org.apache.thrift:libthrift` versions `< 0.24.0` (`CVE-2026-120135` CVSS v4.0 8.2 High), crates.io `thrift` `< 0.23.0` (`RUSTSEC-2026-0435` / `CVE-2026-43868`), and `org.apache.mina:mina-codec` versions `3.0.0` through `3.0.0-M2` (`CVE-2026-118636` CVSS 9.8 Critical)
Update, 12 November 2026 (six russh advisories RUSTSEC-2026-0492..0496 & RUSTSEC-2024-0450, five bsv-rs advisories RUSTSEC-2026-0497..0501, and eazip RUSTSEC-2026-0503): On 12 November 2026 (07:15 to 07:53 UTC), the RustSec Advisory Database merged 12 advisories across russh, bsv-rs, and eazip (commit e57e387b7e):
russh(RUSTSEC-2026-0492through0496andRUSTSEC-2024-0450, PR#3538): AssignsRUSTSEC-2026-0495toCVE-2026-116794(GHSA-vp5q-ff62-jwqv,Agent::confirmbypass in>= 0.50.0-beta.12, < 0.65.0) alongside five additional high-severity advisories:RUSTSEC-2026-0492(CVE-2026-102823/GHSA-47hw-gvq5-r2gm,< 0.63.1, where the SSH client invokedclient::Handlercallbacks for channel numbers the client never opened, allowing a malicious server to spoofexit_statusor channel data on future channels),RUSTSEC-2026-0493(CVE-2026-46702/GHSA-wwx6-x28x-8259,>= 0.34.0, < 0.61.1, unboundedzlib/zlib@openssh.comdecompression buffer before authentication),RUSTSEC-2026-0494(CVE-2026-48110/GHSA-4r3c-5hpg-58qr,>= 0.34.0, < 0.61.0, pre-authSSH_MSG_KEXINITalgorithm name-list allocation DoS),RUSTSEC-2026-0496(CVE-2026-42189/GHSA-f5v4-2wr6-hqmg,< 0.60.1, pre-authSSH_MSG_USERAUTH_INFO_RESPONSEcount vector reservation OOM), andRUSTSEC-2024-0450(CVE-2024-43410/GHSA-vgvv-x7xg-6cqg,< 0.44.1, 4 GiB packet-length buffer allocation).bsv-rs< 0.8.7(RUSTSEC-2026-0497through0501) andeazip< 0.2.7(RUSTSEC-2026-0503):bsv-rsfixes Shamir secret-sharing private-key recovery flaws (RUSTSEC-2026-0501/GHSA-cwxv-4866-5gq2in< 0.8.7), BEEF SPV validation accepting raw non-transaction entries as valid (RUSTSEC-2026-0500/GHSA-j8hr-pjhm-6h27in< 0.8.5), trailing-byte transaction acceptance (RUSTSEC-2026-0498), malformed DER signature acceptance (RUSTSEC-2026-0499/GHSA-9c8r-76f3-m426in< 0.8.6), and non-hexTransaction::from_jsoninputtxids hashing as the 32-byte zero txid (RUSTSEC-2026-0497/GHSA-84xq-3662-pvx5). Meanwhile,eazip0.2.5..0.2.6(RUSTSEC-2026-0503) calledmemchr2(b'\\', b'\0', name.as_bytes())on the symlink’s name instead of its target invalidate_symlink(), allowing Windows..\..\..\symlink extraction escapes (fixed in0.2.7).
Update, 8 November 2026: Between 5 and 8 November 2026, NVD assigned CVE identifiers to the three imgproxy ICO loader advisories and published two follow-up advisories in oauthlib and russh:
imgproxyCVE assignments (8 November 2026):CVE-2026-123614(CVSS 9.8 Critical,GHSA-hff9-5pqw-6w9f,GO-2026-6897) for thedata_size + 14integer overflow and heap buffer overflow inimgproxy 4.0.0before4.0.16;CVE-2026-123615(CVSS 7.5 High,GHSA-494m-4556-wf5p,GO-2026-6895) for thefull_data_size < 40out-of-bounds heap read/write inimgproxy 3.3.0before4.0.17; andCVE-2026-123616(CVSS 7.5 High,GHSA-mmq5-xm89-9pfg,GO-2026-6898) for the unboundeddata_sizememory allocation inimgproxy 3.3.0before4.0.16.- Python
oauthlib4.0.1(CVE-2026-49272, CVSS 8.5 High, published 5 November 2026): Inoauthlib3.3.0before4.0.1(commit77a5f1c8ce,PR #954),DeviceCodeGrantin the RFC 8628 OAuth 2.0 Device Authorization Grant workflow did not require client authentication for confidential clients when exchanging adevice_codeat the token endpoint. Upgrade all the way tooauthlib >= 4.0.1. - Rust
russh(CVE-2026-111062, published 5 November 2026): Inrussh0.34.0-beta.1before0.64.0(commita0ded76bdc,PR #759), the SSH server did not verify that the signature algorithm in aSSH_MSG_USERAUTH_REQUESTpublic-key signature blob matched the outer algorithm field.
Update, 2 November 2026: On 2 November 2026 (11:39 UTC), the RustSec Advisory Database published RUSTSEC-2026-0435 (CVE-2026-43868) for the official Apache Thrift Rust crate (thrift < 0.23.0 on crates.io, ~103M total downloads). Alongside Java’s TProtocol.skip() recursion flaw (CVE-2026-120135) below, Rust’s TBinaryInputProtocol::read_bytes and read_string (src/protocol/binary.rs) read a 4-byte i32 length off the wire, cast it to usize, and allocated vec![0u8; num_bytes] before reading any payload bytes, allowing a 4-byte input to force a 2 GiB allocation (0x7FFFFFFF) or an immediate process abort on a negative i32 (usize::MAX). Fixed in thrift >= 0.23.0 (0.25.0 is current on crates.io), which routes read_bytes through read_binary_len and enforces TConfiguration::max_string_size (default 100 MiB).
TL;DR
Between 22:55 UTC on 30 October and 08:01 UTC on 31 October 2026, the GitHub Advisory Database, NVD, and oss-security published a wave of advisories across seven core libraries and services spanning Go/C, Java, Rust, Python, and Node.js:
imgproxy< 4.0.17ICO C loader heap overflow and OOB write (GHSA-hff9-5pqw-6w9fCritical,GHSA-494m-4556-wf5pHigh, andGHSA-mmq5-xm89-9pfgHigh): Invips/icoload.c,vips_foreign_load_ico_header()read the 32-bit unsigneddata_sizefield from an ICO directory entry and allocatedVIPS_MALLOC(NULL, data_size + BMP_FILE_HEADER_LEN)(data_size + 14). Settingdata_size > UINT32_MAX - 14wrapped the 32-bit addition to a tiny allocation beforevips_foreign_load_read_full()wrote up todata_sizebytes into the heap chunk (GHSA-hff9-5pqw-6w9f). Even afterv4.0.16cappeddata_sizeat 10 MB (GHSA-mmq5-xm89-9pfg), its minimum header check testedfull_data_size < 40(data_size + 14 < 40) instead ofdata_size < 40, so an ICO entry with26 <= data_size <= 39passed the check and overwrote the adjacent glibc heap chunk header when reconstructing the BMP header atactual_data + 8andactual_data + 32(GHSA-494m-4556-wf5p, fixed inv4.0.17).- MariaDB Connector/J
< 3.5.11/< 3.4.5/< 3.3.7arbitrary client file read (CVE-2026-119210) and packet-length heap amplification (CVE-2026-119276,CVE-2026-119279,CVE-2026-119280,CVE-2026-119281): When a MariaDB/MySQL server replies to any query with a0xFBLOCAL INFILEpacket asking the client to upload a local file,ClientMessage.validateLocalFileName()verified that the SQL command the client had sent actually containedLOAD DATA LOCAL INFILE '<file>'. Because the regex matched anywhere in the SQL string (including inside backtick-quoted identifiers, string literals, or comments), a rogue server that returned a table or column name containingLOAD DATA LOCAL INFILE '/etc/passwd'and waited for the application or ORM to runSHOW CREATE TABLEorSELECTquoting that identifier could read any file accessible to the JVM (CVE-2026-119210). russh< 0.65.0silent bypass ofssh-add -cconfirmation (CVE-2026-116794/GHSA-vp5q-ff62-jwqv, High) and unbounded SSH frame allocations (CVE-2026-116773,CVE-2026-116774,CVE-2026-116696): Sincerussh 0.50.0-beta.12(commit3e04597),russh::keys::agent::serverreplaced itsagent.confirm(key)call withfutures::future::ready((agent, true)), signing every SSH authentication request for confirm-constrained (ssh-add -c) keys without ever prompting the user.- Python
oauthlib< 4.0.0client_idauthorization swap (CVE-2026-118669/GHSA-7984-qgvg-3j9c, High): In OAuth 2.0 token grants,authenticate_client(request)setrequest.client, butrequest.client_idremained set to whateverclient_idparameter the caller supplied in the POST body (request.client_id = request.client_id or request.client.client_id). An authenticated low-privilege confidential client could pass another client’sclient_idin the body and passvalidate_grant_type()andvalidate_scopes()under the victim client’s permissions. - npm
follow-redirects1.16.0and1.16.1cross-realmsensitiveHeadersleak (CVE-2026-116689/GHSA-mrwp-f3q8-3g9p, High), Apache Thrift Java< 0.24.0TProtocol.skip()stack overflow (CVE-2026-120135, CVSS v4.0 8.2 High), and Apache MINA3.0.0-M2JavaNativeMessageDecoderRCE (CVE-2026-118636, CVSS 9.8 Critical):follow-redirectscheckedoptions.sensitiveHeaders instanceof Arrayinstead ofArray.isArray(), silently replacing cross-realm arrays (fromvm, Jest, Web Workers, or iframes) with[]and forwarding custom credential headers across cross-origin redirects. In Apache Thrift’s Java library (org.apache.thrift:libthrift < 0.24.0),TProtocol.skip(byte fieldType)calledskip(fieldType, Integer.MAX_VALUE)instead of usingTConfiguration.getRecursionLimit()(64), allowing an unauthenticated peer to triggerStackOverflowErrorby sending deeply nested unknown struct/list/map fields. In the retired Apache MINA3.0.0through3.0.0-M2branch (CVE-2026-118636),JavaNativeMessageDecodercallsObjectInputStream.readObject()on frame bytes with no class filter, exposing any application using that decoder to gadget-chain RCE (migrate to Apache MINA2.2.x).
What to do now: Upgrade imgproxy to >= v4.0.17, org.mariadb.jdbc:mariadb-java-client to >= 3.5.11 (3.4.5 / 3.3.7 / 4.0.0), russh to >= 0.65.0 (and pageant to >= 0.2.5), oauthlib to >= 4.0.1 (4.0.0+), follow-redirects to >= 1.16.2, and org.apache.thrift:libthrift to >= 0.24.0 (and replace any org.apache.mina:mina-codec:3.0.0-M* dependency with Apache MINA 2.2.x).
Affected packages
| Ecosystem | Package | CVE / GHSA | Severity | Affected versions | Fixed version | Vulnerable location |
|---|---|---|---|---|---|---|
| Go / C | github.com/imgproxy/imgproxy/v3 | GHSA-hff9-5pqw-6w9f, GHSA-494m-4556-wf5p, GHSA-mmq5-xm89-9pfg | Critical / High | >= 3.3.0, < 4.0.17 | 4.0.17 | vips_foreign_load_ico_header() in vips/icoload.c |
| Maven | org.mariadb.jdbc:mariadb-java-client | CVE-2026-119210 (GHSA-fhx5-2xqw-2cgm), CVE-2026-119276, 119279, 119280, 119281 | Medium | 3.0.0..3.3.6, 3.4.0..3.4.4, 3.5.0..3.5.10 | 3.3.7, 3.4.5, 3.5.11 (4.0.0) | ClientMessage.validateLocalFileName(), OkPacket.java, StandardReadableByteBuf.java |
| crates.io | russh, pageant | CVE-2026-116794 (GHSA-vp5q-ff62-jwqv), 116773, 116774, 116696, 116775 | High / Medium / Low | russh < 0.65.0; pageant 0.2.0..0.2.4 | russh 0.65.0; pageant 0.2.5 | russh/src/keys/agent/server.rs (Agent::confirm), client/mod.rs, channels/io.rs |
| PyPI | oauthlib | CVE-2026-118669 (GHSA-7984-qgvg-3j9c) | High | < 4.0.0 | 4.0.0 (4.0.1) | validate_token_request() in oauthlib/oauth2/rfc6749/grant_types/ |
| npm | follow-redirects | CVE-2026-116689 (GHSA-mrwp-f3q8-3g9p) | High | 1.16.0, 1.16.1 | 1.16.2 | _sanitizeOptions() in index.js (isArray(options.sensitiveHeaders)) |
| Maven | org.apache.thrift:libthrift | CVE-2026-120135 | CVSS v4.0 8.2 High | < 0.24.0 | 0.24.0 (0.25.0) | TProtocol.skip(byte) in org/apache/thrift/protocol/TProtocol.java |
| Maven | org.apache.mina:mina-codec | CVE-2026-118636 | CVSS 9.8 Critical | 3.0.0 through 3.0.0-M2 (EOL branch) | Migrate to Apache MINA 2.2.x | JavaNativeMessageDecoder (ObjectInputStream.readObject() without class filter) |
Technical analysis
1. imgproxy v4.0.16 and v4.0.17: ICO data_size integer wrap and BMP header reconstruction OOB write (GHSA-hff9-5pqw-6w9f, GHSA-494m-4556-wf5p, GHSA-mmq5-xm89-9pfg)
imgproxy includes a custom libvips C loader (vips/icoload.c) to parse Windows .ico files. Because ICO directory entries store DIB (Device-Independent Bitmap) payloads without the 14-byte BITMAPFILEHEADER, vips_foreign_load_ico_header() allocates a single buffer of data_size + 14 bytes (BMP_FILE_HEADER_LEN = 14), reads the ICO entry payload starting at actual_data = data + 14, and then synthesizes a 14-byte BM file header in front of it while patching the height field inside the 40-byte BITMAPINFOHEADER at actual_data + 8.
In imgproxy < 4.0.16, data_size (a uint32_t read directly from the untrusted ICO header) was passed straight to VIPS_MALLOC(NULL, data_size + BMP_FILE_HEADER_LEN) without a bounds check:
- Sending
data_size = 0xFFFFFFFF(4,294,967,295) wrappeddata_size + 14in 32-bit unsigned arithmetic to13bytes (GHSA-hff9-5pqw-6w9f), or on 64-bit size promotion attempted a ~4 GB allocation per worker from a 23-byte request (GHSA-mmq5-xm89-9pfg).
When commit a821b6a4cb (v4.0.16) added #define MAX_ICO_ENTRY_DATA_SIZE (10 * 1024 * 1024) and a minimum size check for the 40-byte BITMAPINFOHEADER (BMP_BITMAP_INFO_HEADER_LEN = 40), it accidentally compared full_data_size (data_size + 14) against 40 instead of data_size:
--- a/vips/icoload.c
+++ b/vips/icoload.c
@@ -205,7 +205,7 @@ vips_foreign_load_ico_header(VipsForeignLoad *load)
// Ensure the data buffer is large enough to contain the BMP header.
- if (full_data_size < BMP_BITMAP_INFO_HEADER_LEN) {
+ if (data_size < BMP_BITMAP_INFO_HEADER_LEN) {
vips_error("vips_foreign_load_ico_header", "ICO image data is too small to contain a valid BMP header");
VIPS_FREE(data);
return -1;
In v4.0.16, an ICO entry with data_size = 26 had full_data_size = 40, passing the check even though actual_data (data + 14) only had 26 bytes remaining. The loader then read *(uint32_t *)(actual_data + 32) (6 bytes past the allocation) and wrote into heap metadata, crashing the Go worker process in glibc munmap_chunk(). Commit 39fd9e844a (v4.0.17) fixes the comparison to data_size < BMP_BITMAP_INFO_HEADER_LEN.
2. MariaDB Connector/J 3.5.11 / 3.4.5 / 3.3.7: LOAD DATA LOCAL INFILE check satisfied by quoted identifiers (CVE-2026-119210)
In the MySQL/MariaDB wire protocol, any query response can be replaced by the server with a 0xFB<filename> packet asking the client to stream a local file from the client’s filesystem. To stop a rogue or compromised database server from reading arbitrary files such as /etc/passwd or ~/.aws/credentials, MariaDB Connector/J only honors a 0xFB request when allowLocalInfile is enabled (or triggered) and ClientMessage.validateLocalFileName(sql, parameters, fileName, context) confirms that the SQL command the client just sent actually requested <fileName>.
Before commit a4891f877f, validateLocalFileName() matched the SQL command against a regular expression beginning with ^((\s--|#).*(\r\n|\r|\n)|\s*/\*([^*]|\*[^/])*\*/|.)*\s*LOAD\s+(DATA|XML)\s+.... Because the leading |. branch consumed arbitrary characters, including backtick-quoted identifiers and single-quoted string literals, any query that echoed server-supplied metadata inside quotes satisfied the check:
// Regression test in ClientMessageTest.java (commit a4891f877f)
String payload = "LOAD DATA LOCAL INFILE '/etc/passwd'";
Assertions.assertFalse(
ClientMessage.validateLocalFileName(
"SHOW CREATE TABLE `" + payload + "`.`accounts`", null, "/etc/passwd", null));
If an admin tool, migration runner, or ORM connected to an untrusted MariaDB server and ran SHOW TABLES followed by SHOW CREATE TABLE `<table_name>``` (with backticks around the table name), a server returning a table named LOAD DATA LOCAL INFILE ‘/etc/passwd’“ and answering SHOW CREATE TABLE with a 0xFB/etc/passwd packet bypassed validateLocalFileName() and received the contents of /etc/passwd. Commit a4891f877f replaces the regex prefix with a dedicated SQL lexer that skips string literals, quoted identifiers, and comments and only accepts LOAD DATA/XML LOCAL INFILE at the start of a statement.
In the same 3.5.11 / 3.4.5 / 3.3.7 release train, MariaDB also fixed CVE-2026-119279 (commit dbbadc3e21, where 8-byte length-encoded integers 0xFE were narrowed via (int) readLong(), wrapping values above Integer.MAX_VALUE into negative lengths) and CVE-2026-119276 (commit ea8c7b6537, where OkPacket allocated new byte[len] before checking len <= buf.readableBytes()).
3. russh 0.65.0 (CVE-2026-116794), oauthlib 4.0.0 (CVE-2026-118669), follow-redirects 1.16.2 (CVE-2026-116689), and Apache Thrift 0.24.0 (CVE-2026-120135)
russh0.65.0(CVE-2026-116794/GHSA-vp5q-ff62-jwqv): During an async trait refactoring in0.50.0-beta.12(3e04597),russh/src/keys/agent/server.rsreplacedagent.confirm(key.clone()).awaitwith a stub that always returnedtrue. Commit62db6e7defrestores theagent.confirm()call:--- a/russh/src/keys/agent/server.rs +++ b/russh/src/keys/agent/server.rs @@ -347,11 +347,7 @@ let agent = if needs_confirm { - let (agent, ok) = { - let _pk = key.clone(); - Box::new(futures::future::ready((agent, true))) - } - .await; + let (agent, ok) = agent.confirm(key.clone()).await; if !ok { return Ok((agent, false)); }oauthlib4.0.0(CVE-2026-118669/GHSA-7984-qgvg-3j9c): Inoauthlib/oauth2/rfc6749/grant_types/,authorization_code.py,client_credentials.py,resource_owner_password_credentials.py, andrefresh_token.pyauthenticated the calling client viaself.request_validator.authenticate_client(request)(for example via HTTP Basic Auth) and then wroterequest.client_id = request.client_id or request.client.client_id. Becauserequest.client_idwas already populated if the client includedclient_id=victim_clientin the POST form body,request.client_idstayedvictim_clientwhen passed tovalidate_grant_type()andvalidate_scopes(). Commitc951a1d09fcentralizes client validation invalidate_client_confidential()and rejects any request whererequest.client_id != request.client.client_id.follow-redirects1.16.2(CVE-2026-116689/GHSA-mrwp-f3q8-3g9p): Version1.16.0addedoptions.sensitiveHeadersso callers (such as Axios or custom HTTP wrappers) could declare extra headers (likeX-Api-Key) to strip on cross-domain redirects. Because_sanitizeOptions()checkedif (!isArray(options.sensitiveHeaders))usingvalue instanceof Array, passing an array created in a different V8 realm (vm.runInNewContext, Jest test environments, or iframes) failedinstanceof Arrayand resetoptions.sensitiveHeaders = []. Commitb0a7751e9cswitches toArray.isArray(options.sensitiveHeaders).- Apache Thrift Java
0.24.0(CVE-2026-120135): While Thrift’s C++, Go, and Node.js libraries enforced a default recursion limit of64when skipping unknown fields, Java’sTProtocol.skip(byte fieldType)calledthis.skip(fieldType, Integer.MAX_VALUE). Commitdeeebfac25wiresTProtocol.skip(byte)tothis.getTransport().getConfiguration().getRecursionLimit()and throwsTProtocolException(TProtocolException.DEPTH_LIMIT, "Maximum skip depth exceeded").
Detection and remediation
# 1. Check Go, Maven/Gradle, Cargo, Python, and npm lockfiles for affected versions
rg -n 'imgproxy|mariadb-java-client|libthrift|russh|pageant|oauthlib|follow-redirects' \
go.mod pom.xml build.gradle* Cargo.lock requirements*.txt pyproject.toml uv.lock package-lock.json pnpm-lock.yaml yarn.lock 2>/dev/null
# 2. Check running imgproxy container versions
docker ps --format '{{.Image}}' 2>/dev/null | grep -i imgproxy || true
- Upgrade
imgproxyto>= v4.0.17(darthsim/imgproxy:v4.0.17): Do not stop atv4.0.16, which still contains thefull_data_size < 40heap out-of-bounds write (GHSA-494m-4556-wf5p). - Upgrade
org.mariadb.jdbc:mariadb-java-clientto>= 3.5.11(3.4.5/3.3.7/4.0.0) andorg.apache.thrift:libthriftto>= 0.24.0. - Upgrade
russhto>= 0.65.0(pageant >= 0.2.5),oauthlibto>= 4.0.1, andfollow-redirectsto>= 1.16.2.
Timeline
- 2026-04-23: Apache Thrift merges commit
deeebfac25connecting JavaTProtocol.skip()toTConfiguration.getRecursionLimit(), shipping in0.24.0. - 2026-07-11: OAuthLib merges commit
c951a1d09f(PR #920), shipping inoauthlib 4.0.0. - 2026-09-24 to 2026-09-29:
imgproxymerges commitsa821b6a4cb(v4.0.16) and39fd9e844a(v4.0.17) fixing the three ICO loader vulnerabilities. - 2026-10-07 to 2026-10-21: MariaDB merges commits
dbbadc3e21,ea8c7b6537, anda4891f877fand releases Connector/J3.3.7,3.4.5, and3.5.11. - 2026-10-25:
russh(62db6e7def,v0.65.0) andfollow-redirects(b0a7751e9c,v1.16.2) merge and release their fixes. - 2026-10-30 (
22:55to23:13 UTC) and 2026-10-31 (08:01 UTC): The GitHub Advisory Database, NVD, andoss-securitypublish the advisories forimgproxy, MariaDB Connector/J,russh,oauthlib,follow-redirects, and Apache Thrift.
From research to remediation
Check whether this pattern exists in your codebase
Turn this research into a remediation workflow. Scan dependencies and package manifests for similar supply-chain risk, then prioritize fixes with reachability context.
References
- imgproxy advisories GHSA-hff9-5pqw-6w9f, GHSA-494m-4556-wf5p, and GHSA-mmq5-xm89-9pfg (commits a821b6a4cb and 39fd9e844a)
- MariaDB Connector/J advisories GHSA-fhx5-2xqw-2cgm (CVE-2026-119210), GHSA-h599-m3w5-9m7x (CVE-2026-119276), and GHSA-797x-p4mc-jwpm (CVE-2026-119279)
- Eugeny/russh advisory GHSA-vp5q-ff62-jwqv and commit 62db6e7def (CVE-2026-116794: call Agent::confirm)
- oauthlib/oauthlib advisories GHSA-3jp2-3mrg-2vxc (CVE-2026-49272, commit 77a5f1c8ce00) and GHSA-7984-qgvg-3j9c (CVE-2026-118669, commit c951a1d09f)
- follow-redirects advisory GHSA-mrwp-f3q8-3g9p and commit b0a7751e9c (CVE-2026-116689)
- oss-security (2026/10/31/2 and 2026/10/31/3): CVE-2026-120135 Apache Thrift Java TProtocolUtil.skip() recursion limit and CVE-2026-118636 Apache MINA 3.0.0-M2 JavaNativeMessageDecoder deserialization
- oss-security (2026/10/31/3): CVE-2026-118636 Apache MINA 3.0.0-M2 JavaNativeMessageDecoder ObjectInputStream.readObject() RCE