gitpython project gitpython

Name: gitpython project gitpython
Brand: gitpython project

ProduktUS

cpe:2.3:a:gitpython_project:gitpython:*:*:*:*:*:*:*:*

Ein im Bedrohungsgraphen erfasstes Produkt; die Schwachstellen unten betreffen es bekanntermaßen.

KEV-gelistet

EPSS ≥ 10%

nach Schweregrad

4critical12high4medium0low

aktualisiert 2026-10-27

Schwachstellen (35)

Zugehörige CVEs.

Sortierung

ID	Schweregrad	EPSS	ausnutzbar	behoben	veröffentlicht	betroffen
CVE-2022-24439US	critical9.8	6.14% (93rd)	Exploit	3.1.30	2022-12-06	< 3.1.30
CVE-2026-67325US	—	2.21% (83rd)	—	3.1.51	2026-08-01	< 3.1.51
CVE-2026-67323US	—	1.25% (69th)	—	3.1.51	2026-08-01	< 3.1.51
CVE-2023-40267US	critical9.8	1.18% (68th)	—	3.1.32	2023-08-11	< 3.1.32
CVE-2023-41040US	medium6.5	1.09% (65th)	—	kein Fix	2023-08-30	≤ 3.1.34
CVE-2026-73625US	—	0.92% (60th)	—	3.1.54	2026-08-13	< 3.1.54
CVE-2026-76220US	—	0.91% (60th)	—	3.1.58	2026-08-19	< 3.1.58
CVE-2026-73623US	high8.8	0.83% (58th)	—	3.1.54	2026-08-13	< 3.1.54
CVE-2026-76218US	high8.8	0.83% (57th)	—	3.1.58	2026-08-19	< 3.1.58
CVE-2026-78676US	critical9.8	0.78% (56th)	—	3.1.59	2026-08-25	< 3.1.59
CVE-2026-76221US	—	0.77% (56th)	—	3.1.58	2026-08-19	< 3.1.58
CVE-2026-42215US	—	0.75% (55th)	—	3.1.47	2026-05-07	3.1.30 → 3.1.47
CVE-2026-78677US	high7.5	0.65% (51st)	—	3.1.59	2026-08-25	< 3.1.59
CVE-2026-67324US	—	0.64% (51st)	—	3.1.50	2026-08-01	< 3.1.50
CVE-2026-73620US	—	0.57% (47th)	—	3.1.57	2026-08-13	< 3.1.57
CVE-2026-42284US	critical9.8	0.57% (47th)	—	3.1.47	2026-05-07	< 3.1.47
CVE-2026-73624US	—	0.55% (46th)	—	3.1.54	2026-08-13	< 3.1.54
CVE-2026-76219US	—	0.54% (45th)	—	3.1.58	2026-08-19	< 3.1.58
CVE-2026-87819US	high7.5	0.52% (44th)	—	3.1.60	2026-09-09	< 3.1.60
CVE-2026-73622US	—	0.51% (44th)	—	3.1.55	2026-08-13	< 3.1.55
CVE-2023-40590US	high7.8	0.51% (43rd)	—	kein Fix	2023-08-28	≤ 3.1.32
CVE-2026-76222US	high8.2	0.42% (36th)	—	3.1.58	2026-08-19	< 3.1.58
CVE-2026-87817US	high8.8	0.42% (36th)	—	3.1.60	2026-09-09	< 3.1.60
CVE-2026-44243US	high7.1	0.42% (36th)	—	3.1.48	2026-05-07	< 3.1.48
CVE-2026-87818US	medium6.5	0.41% (35th)	—	3.1.60	2026-09-09	< 3.1.60
CVE-2026-78678US	medium6.5	0.41% (35th)	—	3.1.59	2026-08-25	< 3.1.59
CVE-2026-76217US	medium6.5	0.41% (35th)	—	3.1.58	2026-08-19	< 3.1.58
CVE-2026-73619US	—	0.41% (35th)	—	3.1.57	2026-08-13	< 3.1.57
CVE-2026-73621US	—	0.36% (30th)	—	3.1.56	2026-08-13	< 3.1.56
CVE-2026-67322US	—	0.33% (26th)	—	3.1.52	2026-08-01	< 3.1.52
CVE-2024-22190US	high7.8	0.32% (24th)	—	3.1.41	2024-01-11	< 3.1.41
CVE-2026-69097US	high7.3	0.27% (19th)	—	3.1.53	2026-08-03	< 3.1.53
CVE-2026-67326US	high7.8	0.25% (17th)	—	3.1.50	2026-08-01	< 3.1.50
CVE-2026-44244US	—	0.24% (15th)	—	3.1.49	2026-05-07	< 3.1.49
CVE-2026-78675US	high7.8	0.18% (7th)	—	3.1.59	2026-08-25	< 3.1.59

Schwächen (8)

Die Schwächeklassen (CWEs), die die meisten dieser CVEs teilen.

CWE-88Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')12 CVEs
CWE-200Exposure of Sensitive Information to an Unauthorized Actor8 CVEs
CWE-73External Control of File Name or Path6 CVEs
CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')6 CVEs
CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')5 CVEs
CWE-94Improper Control of Generation of Code ('Code Injection')5 CVEs
CWE-20Improper Input Validation3 CVEs
CWE-184Incomplete List of Disallowed Inputs2 CVEs

Datenquellen (1)

Welche Quellen diesen Datensatz belegen und wann.

USNVD / CVE35 CVEs

scry

Produkte tragen bekannte Schwachstellen, sobald sie im Internet exponiert sind. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.

Kostenloser Scan