decidim-core
Affected
- introduced
0, fixed0.30.9(ecosystem)
Fixed versions
0.30.9
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-45573
Decidim: Push subscriptions can be abused for server-side requests
Description
The push-subscription endpoint stores an attacker-controlled delivery URL, and the notification send path becomes an outbound-request sink when VAPID delivery is enabled. The practical result is an authenticated, stored, mostly blind SSRF primitive to arbitrary HTTPS endpoints reachable from the app server.
Technical description
When VAPID delivery is enabled, the notification subscription flow stores the client-supplied push endpoint without checking that it belongs to an approved push service. The send path later passes that stored URL to WebPush.payload_send, turning the subscription into an attacker-controlled outbound request destination.
This is the source-to-sink chain:
subscription.endpoint in the JSON body posted to POST /notifications_subscriptions.params[:endpoint] is stored under user.notification_settings["subscriptions"].user.notifications_subscriptions.values returns that stored endpoint later.build_payload sets endpoint: subscription["endpoint"].WebPush.payload_send(**payload) uses the attacker-supplied endpoint as thedestination.
One spec asserts that the endpoint is persisted exactly as supplied:
# decidim-core/spec/services/decidim/notifications_subscriptions_persistor_spec.rb
expect(user.notifications_subscriptions["auth_code_121"]["endpoint"]).to eq(params[:endpoint])
Another spec asserts that SendPushNotification passes the stored endpoint into WebPush.payload_send:
# decidim-core/spec/services/decidim/send_push_notification_spec.rb
first_notification_payload = {
message:,
endpoint: subscriptions["auth_key_1"]["endpoint"],
p256dh: subscriptions["auth_key_1"]["p256dh"],
auth: subscriptions["auth_key_1"]["auth"],
vapid: a_hash_including(...)
}
expect(WebPush).to receive(:payload_send).with(first_notification_payload)
Impact
POST requests there whenever a notification is pushed.Patches
See https://github.com/decidim/decidim/pull/16714.
Workarounds
Disable the push notifications feature by removing the VAPID keys in the server.
Resource
SSRF
Credits
This issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI.
Medium Basis: The source's own band: MODERATE
0, fixed 0.30.9 (ecosystem)0.30.9
The export has no generic command for this ecosystem.
0.31.0.rc1, fixed 0.31.5 (ecosystem)0.31.5
The export has no generic command for this ecosystem.
0.32.0.rc1, fixed 0.32.0 (ecosystem)0.32.0
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0