Comment by v5v3

Going by the naming, this was reported to Hashicorp prior to 10th June?

And as it's now August, is it redacted as not fixed yet? Why not

CVE-2025-6010 - [REDACTED]