Tools / mitmproxy / Security

Security Deep Dive

mitmproxy

Security posture and CVE patch evidence from tracked releases.

Back to Tool

14 high-severity dependency CVEs affects v12.2.3.

Review the dependency vulnerabilities below.

✗ Signed ✗ SLSA — SBOM ✓ Security policy Quarterly cadence · 45d median Active maintainer

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/9 Present

Signed releases Absent

Latest release artifact signature None

Last verified: 15d ago

SLSA provenance Absent

Attestation predicate level Latest release

Last verified: 15d ago

SBOM published Unknown

GitHub SBOM API Latest release

—

SECURITY.md Present

GitHub repository metadata Repository policy

Checked: 21d ago

Release cadence: quarterly Present

45d median over recent releases Release history

Latest release: 22d ago

Maintainer active Present

Recent commit activity Repository

Last commit: today

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 22d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 22d ago

Signing assets Not active yet

.sig, .crt, cosign.pub, or similar Release asset

Latest release: 22d ago

4.6/10 Security Score

6.5/10 Scorecard

Dependency Exposure 33 transitive dependency CVEs found in the latest SBOM.

Security Score

A composite score aggregating Scorecard performance, CVE patch history, OpenSSF badge tier, and dependency vulnerability exposure. Score ≥ 7.0 is healthy; < 4.0 warrants attention.

epss

0.25 / 0.5

No EPSS data

freshness

1.00 / 1.0

2d stale

scorecard

2.60 / 4.0

Score 6.5/10

cve health

0.25 / 2.5

⚠ No direct scan — 0c/16h transitive CVEs

patch speed

0.50 / 0.5

⚠ Estimated — no CVE patch history

kev exposure

1.50 / 1.5

No KEV exposure

supply chain risk

-1.50 / 10.0

Risk 33.1/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

1.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

6.7

10%

supply chain risk: 33.06 transitive cves: 0c/16h

Provenance trust

provenance trust

6.5

40%

scorecard score: 6.5 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 2d

Operational risk

operational risk

8.5

10%

kev exposure: clear epss max: none

How is this calculated?

The six dimensions group the legacy score signals into weighted categories: direct vulnerability status, patch responsiveness, dependency exposure, provenance checks, maintainer activity, and exploitability risk. The flat component values above remain available for compatibility.

Supply Chain Risk

Risk 33.1/100

0 Transitive critical CVEs

0 KEV-transitive CVEs

47% Dependency freshness

Scorecard

Scorecard 6.5/10

OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.

Check	Score	Reason
Maintained	10	30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
Code-Review	7	Found 13/18 approved changesets -- score normalized to 7
Security-Policy	10	security policy file detected
Dangerous-Workflow	10	no dangerous workflow patterns detected
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
Binary-Artifacts	6	binaries present in source code
License	10	license file detected
Signed-Releases	-1	no releases found
Branch-Protection	-1	internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Fuzzing	0	project is not fuzzed
Pinned-Dependencies	7	dependency not pinned by hash detected -- score normalized to 7
Packaging	10	packaging workflow detected
SAST	4	SAST tool is not run on all commits -- score normalized to 4

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

946 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

High

Medium

Low

Unknown

Still affecting latest (33) All (38)

High 14 Medium 15 Low 4

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2024-4068	high	—	braces	2.3.2	v12.2.3
CVE-2026-26996	high	—	minimatch	9.0.5	v12.2.3
CVE-2026-27606	high	—	rollup	4.53.1	v12.2.3
CVE-2026-27903	high	—	minimatch	9.0.5	v12.2.3
CVE-2026-27904	high	—	minimatch	9.0.5	v12.2.3
CVE-2026-30922	high	—	pyasn1	0.6.2	v12.2.3
CVE-2026-31958	high	—	tornado	6.5.4	v12.2.3
CVE-2026-32141	high	—	flatted	3.3.3	v12.2.3
CVE-2026-33228	high	—	flatted	3.3.3	v12.2.3
CVE-2026-33671	high	—	picomatch	4.0.3	v12.2.3
CVE-2026-35536	high	—	tornado	6.5.4	v12.2.3
CVE-2026-39363	high	—	vite	7.2.2	v12.2.3
CVE-2026-39364	high	—	vite	7.2.2	v12.2.3
CVE-2026-4800	high	—	lodash	4.17.21	v12.2.3
CVE-2024-4067	medium	—	micromatch	3.1.10	v12.2.3
CVE-2024-6485	medium	—	bootstrap	3.4.1	v12.2.3
CVE-2025-13465	medium	—	lodash	4.17.21	v12.2.3
CVE-2025-1647	medium	—	bootstrap	3.4.1	v12.2.3
CVE-2025-64718	medium	—	js-yaml	4.1.0	v12.2.3
CVE-2025-69873	medium	—	ajv	6.12.6	v12.2.3
CVE-2025-71176	medium	—	pytest	8.4.2	v12.2.3
CVE-2026-25645	medium	—	requests	2.32.5	v12.2.3
CVE-2026-27199	medium	—	werkzeug	3.1.5	v12.2.3
CVE-2026-2950	medium	—	lodash	4.17.21	v12.2.3
CVE-2026-33672	medium	—	picomatch	4.0.3	v12.2.3
CVE-2026-33750	medium	—	brace-expansion	1.1.12	v12.2.3
CVE-2026-39365	medium	—	vite	7.2.2	v12.2.3
CVE-2026-41305	medium	—	postcss	8.5.6	v12.2.3
GHSA-78cv-mqj4-43f7	medium	—	tornado	6.5.4	v12.2.3
CVE-2026-27205	low	—	flask	3.1.2	v12.2.3
CVE-2026-3449	low	—	@tootallnate/once	2.0.0	v12.2.3
CVE-2026-4539	low	—	pygments	2.19.2	v12.2.3
GHSA-pjjw-68hj-v9mw	low	—	uv	0.9.28	v12.2.3

Showing 33 of 38