Skip to content
VulniPulse
Advisory severityHigh7.5Apache Software Foundation

High [CVE-2026-76646] remote attacker could cause excessive resource consumption by supplying specially crafted request parameters, potentially resulting in a denial of service condition

This high-severity Apache Software Foundation advisory covers CVE-2026-76646; related products: Apache MyFaces.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-76646 Source published Source updated

VulniPulse record published Record updated

Related products & platforms
Apache Software FoundationUnclassified
Open source advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

A remote attacker could cause excessive resource consumption by supplying specially crafted request parameters, potentially resulting in a denial of service condition.

Older unsupported versions may also be affected.

Users are recommended to upgrade to versions 2.3.12, 2.3-next-M9, 3.0.4, 4.0.4, or 4.1.4, which fix this issue.

Affected product named by the advisory: Apache MyFaces.

Affected versions
  • Apache MyFaces 2.2.0-beta through 2.2.15
  • Apache MyFaces 2.3.0
  • Apache MyFaces 2.3-next-M1 through 2.3-next-M8
  • Apache MyFaces 2.3.1 through 2.3.11
  • Apache MyFaces 3.0.0 through 3.0.3
  • Apache MyFaces 4.0.0 through 4.0.3
  • Apache MyFaces 4.1.0 through 4.1.3

Official advisory · high-confidence parse· fetched 20 days ago·verify at source

Fixed versions
  • 2.3.12
  • 2.3-next-M9
  • 3.0.4
  • 4.0.4
  • 4.1.4

Official advisory · high-confidence parse· fetched 20 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Users are recommended to upgrade to versions 2.3.12, 2.3-next-M9, 3.0.4, 4.0.4, or 4.1.4, which fix this issue.

Official advisory · high-confidence parse· fetched 20 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.