Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed. The problem described was inteded behavior and therefore not a bug.
Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed.
Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed.
Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is not needed.
Rejected reason: Red Hat Product Security has determined that this CVE is not a security vulnerability.
Rejected reason: This CVE was previously published at https://bugzilla.redhat.com/show_bug.cgi?id=2262978 but later rejected for the following reason: The flaw requires an attacker to have superuser c
Rejected reason: “This CVE ID is Rejected and will not be used. The issue was determined to not be a vulnerability.”
Rejected reason: This CVE id was assigned to an issue which was later deemed not security relevant.
Rejected reason: This CVE id was assigned to an issue which was later deemed not security relevant.
Rejected reason: This CVE id was assigned to an issue which was later deemed not security relevant.
Rejected reason: This CVE was marked as fixed, but due to other code landing - was not actually fixed. It was subsequently fixed in CVE-2025-5986.
Rejected reason: Test CVE
Rejected reason: The reserved CVE was never used.
Rejected reason: Considered by the maintainers a bug scenario experienced rather than a vulnerability.
Rejected reason: This CVE ID has been rejected by its CNA as it was not a security issue.
Rejected reason: This CVE ID has been rejected by its CNA as it was not a security issue.
Rejected reason: This CVE was assigned in error.
Rejected reason: This CVE was assigned in error.
Rejected reason: This CVE ID is Rejected because the issue was not a vulnerability. The data field reported is not attacker controlled.
Rejected reason: After analysis, the originally reported behaviour was determined not to constitute a security vulnerability. The findings were parser-strictness defects without an exploitable framing
Page 1+ Next →