Unassigned Severity for (Critical) CVEs

### Current Behavior

Hello all,

I am using 4.12 version of Dep track. I see that some CVEs are always unassigned.



All the schedulers are running without any issues. Please guide on how to resolve this.

Thank you

### Steps to Reproduce

Login into Dependancy track and search for **CVE-2024-31573**

### Expected Behavior

CVE-2024-31573 should have status as Critical as mentioned here https://ossindex.sonatype.org/vulnerability/CVE-2024-31573?component-type=maven&component-name=org.xmlunit%2Fxmlunit-core&utm_source=dependency-track&utm_medium=integration&utm_content=v4.12.1

### Dependency-Track Version

4.12.x

### Dependency-Track Distribution

Container Image

### Database Server

PostgreSQL

### Database Server Version

_No response_

### Browser

Google Chrome

### Checklist

- [x] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [x] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this defect was already reported