Question about CVE-2026-0637 being referenced in two different advisories
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 34
- Forks
- 75
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 5
Description
Hi Team,
I noticed what seems to be an inconsistency regarding CVE-2026-0637 in your security advisories documentation.
The same CVE appears in these two advisories:
- https://github.com/wso2/docs-security/blob/main/en/docs/security-announcements/security-advisories/2026/WSO2-2025-4829.md
- https://github.com/wso2/docs-security/blob/main/en/docs/security-announcements/security-advisories/2026/WSO2-2025-4897.md
From my reading, these advisories do not appear to describe the same vulnerability, yet they both reference CVE-2026-0637.
Could you please clarify:
- Whether CVE-2026-0637 is correctly assigned in both advisories;
- If one of the references is a typo or copy/paste error;
- Which advisory should be considered the canonical reference for this CVE.
Thank you for your help and for maintaining these security announcements.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the CVE-2026-0637 references in WSO2-2025-4829.md and WSO2-2025-4897.md. Check whether both advisories describe the same vulnerability, then ask the maintainers to confirm the correct assignment and canonical advisory. Done means the discrepancy is clarified and any confirmed documentation error is corrected.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100