← Back
CLEANSTART-2026-YG75447
Vulnerability in argo-cd-fips (CLEANSTART-2026-YG75447)
Summary
vulnerability in argo-cd-fips (CLEANSTART-2026-YG75447). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `3.2.5-r0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CLEANSTART-2026-YG75447** has been found in argo-cd-fips.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade argo-cd-fips to **3.2.5-r0** or later.
If unsure, ask your IT team or search "argo-cd-fips CLEANSTART-2026-YG75447" on the vendor's site.
CLEANSTART-2026-YG75447 (argo-cd-fips) —
Patched: `3.2.5-r0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (unclassified) exists in argo-cd-fips.
📍 Affected scope
argo-cd-fips — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.2.5-r0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'argo-cd-fips' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'argo-cd-fips' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `argo-cd-fips` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade argo-cd-fips to 3.2.5-r0ステージング環境で 3.2.5-r0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
CleanStart
argo-cd-fips
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.5-r0"}]}]
References
- advisory https://github.com/cleanstart-dev/cleanstart-security-advisories/tree/main/advisories/2026/CLEANSTART-2026-YG75447.json
- web https://osv.dev/vulnerability/CVE-2025-55190
- web https://osv.dev/vulnerability/CVE-2025-55191
- web https://osv.dev/vulnerability/CVE-2025-58183
- web https://osv.dev/vulnerability/CVE-2025-58185
- web https://osv.dev/vulnerability/CVE-2025-58187
- web https://osv.dev/vulnerability/CVE-2025-58188
- web https://osv.dev/vulnerability/CVE-2025-58189
- web https://osv.dev/vulnerability/CVE-2025-59537
- web https://osv.dev/vulnerability/CVE-2025-59538
- web https://osv.dev/vulnerability/CVE-2025-61723
- web https://osv.dev/vulnerability/CVE-2025-61724
- web https://osv.dev/vulnerability/CVE-2025-61725
- web https://osv.dev/vulnerability/CVE-2026-1229
- web https://osv.dev/vulnerability/CVE-2026-24051
- web https://osv.dev/vulnerability/CVE-2026-25679
- web https://osv.dev/vulnerability/CVE-2026-25934
- web https://osv.dev/vulnerability/CVE-2026-27139
- web https://osv.dev/vulnerability/CVE-2026-27142
- web https://osv.dev/vulnerability/CVE-2026-33186
- web https://osv.dev/vulnerability/ghsa-2v5j-vhc3-9cwm
- web https://osv.dev/vulnerability/ghsa-2vgg-9h3w-qbr4
- web https://osv.dev/vulnerability/ghsa-2xsj-vh29-9cwm
- web https://osv.dev/vulnerability/ghsa-3wgm-2mw2-vh5m
- web https://osv.dev/vulnerability/ghsa-4x4m-3c2p-qppc
- web https://osv.dev/vulnerability/ghsa-6v2p-p543-phr9
- web https://osv.dev/vulnerability/ghsa-92cp-5422-2m47
- web https://osv.dev/vulnerability/ghsa-93mq-9ffx-83m2
- web https://osv.dev/vulnerability/ghsa-f6x5-jh6r-wrfv
- web https://osv.dev/vulnerability/ghsa-hj2p-8wj8-pfq4
- web https://osv.dev/vulnerability/ghsa-j5w8-q4qc-rx2x
- web https://osv.dev/vulnerability/ghsa-mh63-6h87-95cp
- web https://osv.dev/vulnerability/ghsa-mw99-9chc-xw7r
- web https://nvd.nist.gov/vuln/detail/CVE-2025-55190
- web https://nvd.nist.gov/vuln/detail/CVE-2025-55191
- web https://nvd.nist.gov/vuln/detail/CVE-2025-58183
- web https://nvd.nist.gov/vuln/detail/CVE-2025-58185
- web https://nvd.nist.gov/vuln/detail/CVE-2025-58187
- web https://nvd.nist.gov/vuln/detail/CVE-2025-58188
- web https://nvd.nist.gov/vuln/detail/CVE-2025-58189
- web https://nvd.nist.gov/vuln/detail/CVE-2025-59537
- web https://nvd.nist.gov/vuln/detail/CVE-2025-59538
- web https://nvd.nist.gov/vuln/detail/CVE-2025-61723
- web https://nvd.nist.gov/vuln/detail/CVE-2025-61724
- web https://nvd.nist.gov/vuln/detail/CVE-2025-61725
- web https://nvd.nist.gov/vuln/detail/CVE-2026-1229
- web https://nvd.nist.gov/vuln/detail/CVE-2026-24051
- web https://nvd.nist.gov/vuln/detail/CVE-2026-25679
- web https://nvd.nist.gov/vuln/detail/CVE-2026-25934
- web https://nvd.nist.gov/vuln/detail/CVE-2026-27139
- web https://nvd.nist.gov/vuln/detail/CVE-2026-27142
- web https://nvd.nist.gov/vuln/detail/CVE-2026-33186