<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 13 Nov 2026 08:32:13 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-86323</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-86323</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-86323</guid>
    </item>
    <item>
      <title>GHSA-88rx-hv2v-x9jw</title>
      <link>https://db.gcve.eu/vuln/ghsa-88rx-hv2v-x9jw</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-88rx-hv2v-x9jw</guid>
    </item>
    <item>
      <title>RHSA-2026:99949 — Red Hat Security Advisory: Satellite 6.16.15 Async Update</title>
      <link>https://db.gcve.eu/vuln/rhsa-2026:99949</link>
      <description>&lt;p&gt;sequoia-openpgp: sequoia-openpgp: Cryptographic integrity compromise via key flag confusion crass: crass: Denial of Service via crafted scientific notation in CSS crass: crass: Denial of Service via excessive recursion when processing comments puma: Puma: HTTP Request Smuggling via Underscore Header Name Confusion foreman: Cross-tenant disclosure of template revisions via unauthorized audit lookup rubygem-katello: Cross-tenant Content View Filter rule access and modification via unauthorized parent filter lookup foreman: authorization flaw in the Foreman::Controller::UserAware#find_user handling used by Api::V2::PersonalAccessTokensController foreman: authorization flaw in the mail-notification endpoints implemented by Api::V2::MailNotificationsController foreman: authorization flaw in the Foreman::Controller::UserAware handling used by Api::V2::SshKeysController pulpcore: pulpcore: file:// scheme allowlist bypass in content upload file_url field enables arbitrary file read and Pulp Container registry signing key theft pyjwt: pyjwt: Verification key substitution via unvalidated JWKS redirects pyjwt: PyJWT: Authentication bypass via improper public key validation pyjwt: pyjwt: Token forgery via improper Unicode byte-order mark handling pyjwt: pyjwt: Token forgery via acceptance of public JWK containers as HMAC secrets pulp-rpm: Distribution tree publish creates directories from .treeinfo ids candlepin: candlepin: broken object-level authorization via VerifyAuthorizationFilter…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;sequoia-openpgp: sequoia-openpgp: Cryptographic integrity compromise via key flag confusion crass: crass: Denial of Service via crafted scientific notation in CSS crass: crass: Denial of Service via excessive recursion when processing comments puma: Puma: HTTP Request Smuggling via Underscore Header Name Confusion foreman: Cross-tenant disclosure of template revisions via unauthorized audit lookup rubygem-katello: Cross-tenant Content View Filter rule access and modification via unauthorized parent filter lookup foreman: authorization flaw in the Foreman::Controller::UserAware#find_user handling used by Api::V2::PersonalAccessTokensController foreman: authorization flaw in the mail-notification endpoints implemented by Api::V2::MailNotificationsController foreman: authorization flaw in the Foreman::Controller::UserAware handling used by Api::V2::SshKeysController pulpcore: pulpcore: file:// scheme allowlist bypass in content upload file_url field enables arbitrary file read and Pulp Container registry signing key theft pyjwt: pyjwt: Verification key substitution via unvalidated JWKS redirects pyjwt: PyJWT: Authentication bypass via improper public key validation pyjwt: pyjwt: Token forgery via improper Unicode byte-order mark handling pyjwt: pyjwt: Token forgery via acceptance of public JWK containers as HMAC secrets pulp-rpm: Distribution tree publish creates directories from .treeinfo ids candlepin: candlepin: broken object-level authorization via VerifyAuthorizationFilter…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/rhsa-2026:99949</guid>
    </item>
  </channel>
</rss>
