Skip to content

Vulnerabilities in Agent v7.64.3 #36592

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
JideEngDev opened this issue May 1, 2025 · 7 comments
Closed

Vulnerabilities in Agent v7.64.3 #36592

JideEngDev opened this issue May 1, 2025 · 7 comments

Comments

@JideEngDev
Copy link

Could you please help in resolving these following vulnerabilities?

@sgnn7
Copy link
Contributor

sgnn7 commented May 2, 2025

Hi @JideEngDev ,

For these, I'd just make sure to use the newest releases when they become available.

As for the third one, it's a bit outside of the scope of my context but maybe someone else familiar can answer.

@JideEngDev
Copy link
Author

@sgnn7 Thanks for responding. Do you have an idea when the next agent version will be released?

@sgnn7
Copy link
Contributor

sgnn7 commented May 2, 2025

@JideEngDev We don't provide exact dates for releases as it's an iterative process until we are happy with the artifacts but what I can say is that 7.65 seems to be in the tail end of QA so you shouldn't be waiting long.

@sgnn7
Copy link
Contributor

sgnn7 commented May 6, 2025

@JideEngDev Agent v7.65.0 was just released :)

@JideEngDev
Copy link
Author

Thank you @sgnn7! We can close this

@JideEngDev
Copy link
Author

@sgnn7 The latest version resolved these vulnerabilities. It also introduced a new one :

CVE-2025-46569 - github.com/open-policy-agent/opa:v0.70.0

@sgnn7
Copy link
Contributor

sgnn7 commented May 8, 2025

Hi @JideEngDev ,
Glad to see that your original issue is resolved .

As for your follow-up detection, it's being worked on:

On a broader scale, given that all software contains numerous (and in our case countless) third-party dependencies, you will likely see this rolling fix pattern since it's a perpetual ongoing effort to remediate new detections as they come up. My suggestion is that you keep an eye on pull requests and our release cycles to have a sense of when they will be fixed.

For now, I'll close this issue so that we don't muddy the original submission remediation and thank you for your report!

@sgnn7 sgnn7 closed this as completed May 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants