CVE-2026-86323
A flaw was found in Foreman’s Api::V2::MailNotificationsController, …
A flaw was found in Foreman’s Api::V2::MailNotificationsController, where authorization checks on user-specific mail-notification resources are insufficient. The GET /api/v2/users/:id/mail_notifications endpoint resolves the target account using User.find(params[:id]) without verifying that the authenticated user is authorized to access that user’s notification configuration. Additionally, the POST and PUT /api/v2/users/:user_id/mail_notifications paths call deny_access when the requester is unauthorized but fail to halt execution, allowing the request to continue and persist the unauthorized change despite a 403 response or subsequent DoubleRenderError. This can allow a user to disclose another user’s mail-notification configuration, including mail_query values, and, where write permissions apply, modify or create notification settings for another user.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- access.redhat.com/security/cve/CVE-2026-86323
- bugzilla.redhat.com/show_bug.cgi?id=2529290
- access.redhat.com/errata/RHSA-2026:99949
- access.redhat.com/errata/RHSA-2026:99950
- access.redhat.com/errata/RHSA-2026:99952
- access.redhat.com/errata/RHSA-2026:100120
- nvd.nist.gov/vuln/detail/CVE-2026-86323
- cve.org/CVERecord?id=CVE-2026-86323
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.