High CVE in Alertmanager v0.25.0 Image

[AdeepKrishnaKeelar]

There has been a high CVE in the Alertmanager v0.25.0 Image, running the scan, getting the following result -

bin/alertmanager (gobinary)

Total: 1 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 1, CRITICAL: 0)

┌──────────────────┬────────────────┬──────────┬────────┬───────────────────┬───────────────┬──────────────────────────────────────────────┐
│     Library      │ Vulnerability  │ Severity │ Status │ Installed Version │ Fixed Version │                    Title                     │
├──────────────────┼────────────────┼──────────┼────────┼───────────────────┼───────────────┼──────────────────────────────────────────────┤
│ golang.org/x/net │ CVE-2022-41723 │ HIGH     │ fixed  │ v0.4.0            │ 0.7.0         │ avoid quadratic complexity in HPACK decoding │
│                  │                │          │        │                   │               │ https://avd.aquasec.com/nvd/cve-2022-41723   │
└──────────────────┴────────────────┴──────────┴────────┴───────────────────┴───────────────┴──────────────────────────────────────────────┘

bin/amtool (gobinary)

Total: 1 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 1, CRITICAL: 0)

┌──────────────────┬────────────────┬──────────┬────────┬───────────────────┬───────────────┬──────────────────────────────────────────────┐
│     Library      │ Vulnerability  │ Severity │ Status │ Installed Version │ Fixed Version │                    Title                     │
├──────────────────┼────────────────┼──────────┼────────┼───────────────────┼───────────────┼──────────────────────────────────────────────┤
│ golang.org/x/net │ CVE-2022-41723 │ HIGH     │ fixed  │ v0.4.0            │ 0.7.0         │ avoid quadratic complexity in HPACK decoding │
│                  │                │          │        │                   │               │ https://avd.aquasec.com/nvd/cve-2022-41723   │
└──────────────────┴────────────────┴──────────┴────────┴───────────────────┴───────────────┴──────────────────────────────────────────────┘

Is there any chance of getting this issue addressed in the build of the image in the upcoming updates or any help on this matter would be highly appreciated!