CVEs in Prometheus-Adapter

[simrangera99]

What happened?:
Following CVE's are being reported in Prometheus Adapter:
CVE-2025-22868 | HIGH
CVE-2025-4673 | MEDIUM
CVE-2025-0913 | MEDIUM
GHSA-fv92-fjc5-jj9h |
CVE-2025-22872 | MEDIUM
CVE-2024-34158 | HIGH
CVE-2024-24791 | HIGH
CVE-2024-34156 | HIGH
CVE-2024-24790 | CRITICAL

What did you expect to happen?:
Fix the CVE

Please provide the prometheus-adapter config:

Please provide the HPA resource used for autoscaling:

Please provide the HPA status:

Please provide the prometheus-adapter logs with -v=6 around the time the issue happened:

Anything else we need to know?:

Environment:

• prometheus-adapter version:
• prometheus version:
• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration:
• Other info:

[k8s-ci-robot]

This issue is currently awaiting triage.

If prometheus-adapter contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[kevincantu]

This matters for many users.

/remove-lifecycle rotten

[m-barthelemy]

Hi, is there a plan to address these findings?

[saripurigopi]

Hi, I'd like to work on this. I'll open a PR to bump vulnerable dependencies shortly.