Поиск уязвимостей
Количество 7
Количество 7
CVE-2026-93326
A build step for a Git source, crafted in a specific way, can bypass some policy validation rules. A malicious build definition can make the repository look like it is coming from a different remote URL than it really is when Git clone is happening. If policy is doing more stricter validation, for example based on commit SHA, commit data, or signatures, then all these validations still apply correctly.
CVE-2026-93326
A build step for a Git source, crafted in a specific way, can bypass some policy validation rules. A malicious build definition can make the repository look like it is coming from a different remote URL than it really is when Git clone is happening. If policy is doing more stricter validation, for example based on commit SHA, commit data, or signatures, then all these validations still apply correctly.
CVE-2026-93326
A build step for a Git source, crafted in a specific way, can bypass some policy validation rules. A malicious build definition can make the repository look like it is coming from a different remote URL than it really is when Git clone is happening. If policy is doing more stricter validation, for example based on commit SHA, commit data, or signatures, then all these validations still apply correctly.
CVE-2026-93326
Crafted Git build source can bypass certain policy validation
CVE-2026-93326
A build step for a Git source, crafted in a specific way, can bypass s ...
ROS-20261023-80-0213
Уязвимость buildkit
ROS-20261023-73-0212
Уязвимость buildkit
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2026-93326 A build step for a Git source, crafted in a specific way, can bypass some policy validation rules. A malicious build definition can make the repository look like it is coming from a different remote URL than it really is when Git clone is happening. If policy is doing more stricter validation, for example based on commit SHA, commit data, or signatures, then all these validations still apply correctly. | 0% Низкий | около 1 месяца назад | ||
CVE-2026-93326 A build step for a Git source, crafted in a specific way, can bypass some policy validation rules. A malicious build definition can make the repository look like it is coming from a different remote URL than it really is when Git clone is happening. If policy is doing more stricter validation, for example based on commit SHA, commit data, or signatures, then all these validations still apply correctly. | CVSS3: 5.9 | 0% Низкий | около 1 месяца назад | |
CVE-2026-93326 A build step for a Git source, crafted in a specific way, can bypass some policy validation rules. A malicious build definition can make the repository look like it is coming from a different remote URL than it really is when Git clone is happening. If policy is doing more stricter validation, for example based on commit SHA, commit data, or signatures, then all these validations still apply correctly. | 0% Низкий | около 1 месяца назад | ||
CVE-2026-93326 Crafted Git build source can bypass certain policy validation | 0% Низкий | около 1 месяца назад | ||
CVE-2026-93326 A build step for a Git source, crafted in a specific way, can bypass s ... | 0% Низкий | около 1 месяца назад | ||
ROS-20261023-80-0213 Уязвимость buildkit | CVSS3: 7.1 | 0% Низкий | 26 дней назад | |
ROS-20261023-73-0212 Уязвимость buildkit | CVSS3: 7.1 | 0% Низкий | 26 дней назад |
Уязвимостей на страницу