Skip to content

chore(core): mitigate CVEs based on report 2026-06-29#2557

Open
diafour wants to merge 4 commits into
mainfrom
chore/core/cve-migitation-2026-06-29
Open

chore(core): mitigate CVEs based on report 2026-06-29#2557
diafour wants to merge 4 commits into
mainfrom
chore/core/cve-migitation-2026-06-29

Conversation

@diafour

@diafour diafour commented Jun 29, 2026

Copy link
Copy Markdown
Member

Description

Mitigate Trivy-reported High/Critical vulnerabilities in dependencies.

Updated CVE-related replacements:

  • golang.org/x/crypto -> v0.52.0
  • golang.org/x/net -> v0.55.0
  • golang.org/x/oauth2 -> v0.34.0
  • golang.org/x/sys -> v0.45.0

See also support PRs:

Why do we need it, and what problem does it solve?

Mitigate CVE list:

CVE-2026-25680
CVE-2026-25681
CVE-2026-27136
CVE-2026-33814
CVE-2026-39821
CVE-2026-39827
CVE-2026-39828
CVE-2026-39829
CVE-2026-39830
CVE-2026-39832
CVE-2026-39835
CVE-2026-42502
CVE-2026-42506
CVE-2026-42508
CVE-2026-46595
CVE-2026-46597

What is the expected result?

No Critical and High severity CVEs in the Trivy report.

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: core
type: chore
summary: Bump dependencies to mitigate CVEs based on report 2026-06-29.

@diafour diafour force-pushed the chore/core/cve-migitation-2026-06-29 branch from 4413ea4 to 517ae09 Compare June 30, 2026 14:24
@diafour diafour added this to the v1.10.0 milestone Jun 30, 2026
@diafour diafour force-pushed the chore/core/cve-migitation-2026-06-29 branch 2 times, most recently from 0c32068 to 4d8e036 Compare July 1, 2026 15:55
- Mitigate Trivy-reported High/Critical vulnerabilities in dependencies.

Updated CVE-related replacements:
golang.org/x/crypto -> v0.52.0
golang.org/x/net -> v0.55.0
golang.org/x/oauth2 -> v0.34.0

- Add CVE-2026-41579 justification in VEX format for for github.com/opencontainers/runc dependency.

Signed-off-by: Ivan Mikheykin <ivan.mikheykin@flant.com>
@diafour diafour force-pushed the chore/core/cve-migitation-2026-06-29 branch from 4d8e036 to 944c100 Compare July 2, 2026 12:43
Signed-off-by: Maksim Khimchenko <maksim.khimchenko@flant.com>
@diafour diafour requested a review from LopatinDmitr July 2, 2026 15:21
diafour added 2 commits July 2, 2026 18:25
Signed-off-by: Ivan Mikheykin <ivan.mikheykin@flant.com>
…6-29' into chore/core/cve-migitation-2026-06-29
@diafour diafour marked this pull request as ready for review July 2, 2026 15:27
shell:
install:
- |
echo "I want to rebuild my branch! 1"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't forget to delete.

],
"status": "not_affected",
"justification": "vulnerable_code_cannot_be_controlled_by_adversary",
"impact_statement": "Уязвимость CVE-2026-41579 требует запуска runc на злонамеренном container image, в котором /dev представлен как symlink, чтобы спровоцировать ограниченное нарушение целостности host filesystem при подготовке rootfs. В образе virt-handler наличие зависимости github.com/opencontainers/runc является транзитивным, однако компонент не предоставляет атакующему управляемый путь для запуска runc на произвольном malicious image с описанными предпосылками. Поэтому уязвимый сценарий для virt-handler и сопутствующего исполнимого файла virt-chroot в рамках ожидаемой модели эксплуатации компонента не достижим.",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Russian?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah

],
"status": "not_affected",
"justification": "vulnerable_code_cannot_be_controlled_by_adversary",
"impact_statement": "Уязвимость CVE-2026-41579 требует запуска runc на специально подготовленном malicious image с /dev в виде symlink, чтобы при подготовке rootfs вызвать ограниченное нарушение целостности файловой системы хоста. В образе virt-launcher зависимость github.com/opencontainers/runc присутствует транзитивно, но компонент не предоставляет атакующему произвольный путь исполнения runc на подконтрольном image с указанными предпосылками. Следовательно, описанный сценарий эксплуатации для virt-launcher в штатной модели использования компонента не достижим.",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Russian?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants