June Public announcement

[anjai94]

public announcement has been done for below security advisories.

• WSO2-2025-4227_CVE-2025-5802.pdf
• WSO2-2026-4844_CVE-2026-4103.pdf
• WSO2-2026-5174_CVE-2026-3416.pdf
• WSO2-2026-4608_CVE-2026-3863.pdf
• WSO2-2026-5164_CVE-2026-3096.pdf

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Warning

Review limit reached

@anjai94, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 57 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 58b4a3e0-e413-45a8-93d5-9baed8451834

📥 Commits

Reviewing files that changed from the base of the PR and between 88a3bc9 and 7649c3d.

📒 Files selected for processing (3)

• en/docs/security-announcements/security-advisories/2026/WSO2-2026-4844.md
• en/docs/security-reporting/reward-and-acknowledgement-program/hall-of-fame.md
• en/mkdocs.yml

📝 Walkthrough

Walkthrough

This PR adds five new security advisory documents (WSO2-2026-5174, WSO2-2026-5164, WSO2-2026-4844, WSO2-2026-4608, WSO2-2025-4227) covering various CVEs, each including metadata, affected products, description, impact, and remediation guidance. The 2026 advisories index and mkdocs navigation are updated with corresponding links/entries. The hall-of-fame table formatting is also adjusted with a spacing change and an inserted blank row.

Changes

Cohort / File(s)	Change Summary
WSO2-2026-5174.md	New advisory: predictable webhook HMAC secrets
WSO2-2026-5164.md	New advisory: potential reverse tabnabbing
WSO2-2026-4844.md	New advisory: stored XSS in Publisher/Developer Portal
WSO2-2026-4608.md	New advisory: uncontrolled memory consumption via large file processing
WSO2-2025-4227.md	New advisory: username enumeration in self-registration flow
2026-advisories.md, mkdocs.yml	Added index links and navigation entries for the five new advisories
hall-of-fame.md	Table formatting adjustment and inserted blank row

Suggested reviewers: ayomawdb, pathberiya, DMHP

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description does not follow the required template and is missing all mandatory sections beyond a short summary list.	Fill in the template sections for Purpose, Goals, Approach, User stories, Release note, Documentation, and the remaining required items.
Title check	❓ Inconclusive	The title is related to the change, but it is generic and does not clearly identify the security advisory announcement.	Rename it to clearly state the main change, such as a public announcement for the listed security advisories.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@en/docs/security-announcements/security-advisories/2026/WSO2-2026-4608.md`:
- Around line 1-15: The markdown file still has a stale placeholder document
before the real advisory metadata, so the actual security advisory front matter
is not being recognized. Remove the initial stub content and keep only the
single front matter block used by the WSO2-2026-4608 advisory, ensuring the
title/category/published/version/severity/cvss fields are the only header
metadata before any body content.

In `@en/mkdocs.yml`:
- Line 132: The navigation entry in mkdocs should use a key that matches the
advisory it points to, since the current WSO2-2025-4249 label is paired with the
WSO2-2025-4227.md document and will show the wrong advisory name in the sidebar.
Update the nav item key in the mkdocs configuration to the correct advisory
identifier so the label and target markdown file are consistent.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c4d85ac7-f4bc-4c1f-8d07-e9c92ad8c273

📥 Commits

Reviewing files that changed from the base of the PR and between dd51001 and 88a3bc9.

📒 Files selected for processing (8)

• en/docs/security-announcements/security-advisories/2026/2026-advisories.md
• en/docs/security-announcements/security-advisories/2026/WSO2-2025-4227.md
• en/docs/security-announcements/security-advisories/2026/WSO2-2026-4608.md
• en/docs/security-announcements/security-advisories/2026/WSO2-2026-4844.md
• en/docs/security-announcements/security-advisories/2026/WSO2-2026-5164.md
• en/docs/security-announcements/security-advisories/2026/WSO2-2026-5174.md
• en/docs/security-reporting/reward-and-acknowledgement-program/hall-of-fame.md
• en/mkdocs.yml