You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Venkateswara Adithya Kumar Obilisetty via users <us...@cxf.apache.org> on 2026/10/14 18:33:15 UTC

Question on affected-version data for CXF CVEs fixed in 3.6.12

Hello CXF Team,

I'm reaching out about a version-data discrepancy on NVD for the following
CVEs affecting CXF:

CVE-2026-50633
CVE-2026-50628
CVE-2026-50632
CVE-2026-50627
CVE-2026-49875
CVE-2026-50645
CVE-2026-50630
CVE-2026-50629
CVE-2026-50631
CVE-2026-50623
CVE-2026-50634

All of these are fixed in cxf-3.6.12. On each NVD page, the "Affected
Products" section correctly shows "0 < 3.6.12 (semver)". However, the
"Known Affected Software Configurations" section does not reflect this
bound, and cxf-3.6.12 is still listed as affected there.

Vulnerability scanners appear to use the configuration data, so they report
3.6.12 and later as vulnerable to these CVEs.

Could this be a clerical error in the CVE records published by the CXF /
ASF side?
If so, could the records be corrected?

I have also written to NVD to request a correction on their end.

Thank you for maintaining the project!

Best
Adithya

Re: Question on affected-version data for CXF CVEs fixed in 3.6.12

Posted by Colm O hEigeartaigh <co...@apache.org>.
Hi,

Unfortunately there is not much we can do on our side at the ASF.
Hopefully they will respond to your request and update their records.

Colm.

On Wed, Oct 14, 2026 at 7:33 PM Venkateswara Adithya Kumar Obilisetty
via users <us...@cxf.apache.org> wrote:
>
> Hello CXF Team,
>
> I'm reaching out about a version-data discrepancy on NVD for the following
> CVEs affecting CXF:
>
> CVE-2026-50633
> CVE-2026-50628
> CVE-2026-50632
> CVE-2026-50627
> CVE-2026-49875
> CVE-2026-50645
> CVE-2026-50630
> CVE-2026-50629
> CVE-2026-50631
> CVE-2026-50623
> CVE-2026-50634
>
> All of these are fixed in cxf-3.6.12. On each NVD page, the "Affected
> Products" section correctly shows "0 < 3.6.12 (semver)". However, the
> "Known Affected Software Configurations" section does not reflect this
> bound, and cxf-3.6.12 is still listed as affected there.
>
> Vulnerability scanners appear to use the configuration data, so they report
> 3.6.12 and later as vulnerable to these CVEs.
>
> Could this be a clerical error in the CVE records published by the CXF /
> ASF side?
> If so, could the records be corrected?
>
> I have also written to NVD to request a correction on their end.
>
> Thank you for maintaining the project!
>
> Best
> Adithya