CVE-2026-41105
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedServer-side request forgery (ssrf) in Azure Notification Service allows an authorized attacker to elevate privileges over a network.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceServer-side request forgery (SSRF) vulnerability in Azure Notification Service enables an already-authorized attacker to make the service perform unintended network requests, potentially reaching internal resources or cloud metadata endpoints to escalate privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Azure Monitor Action Groups in your subscriptionRun 'Get-AzActionGroup' in Azure PowerShell or check in Azure Portal under Monitor > Action groups to list all configured Action GroupsAffected if Any Action Group exists in the subscription - the vulnerability affects all versions of the notification system
-
Review notification endpoints configured in Action GroupsInspect each Action Group's notification receivers (email, webhook, Azure Function, Logic App, SMS, etc.) using 'Get-AzActionGroup -ResourceGroupName <name> -Name <group>'Affected if Action Groups contain webhook or HTTP(S) receivers that could accept maliciously crafted destinations
-
Check for Azure Activity Log entries from NotificationServiceQuery Azure Activity Log for events where 'operationName' contains 'Notification' or 'Alert' and 'caller' indicates the notification service, looking for unexpected outbound requestsAffected if Logs show outbound requests to unexpected or internal IP ranges (especially 169.254.169.254 for metadata, 10.x.x.x, 192.168.x.x)
-
Audit network egress rules for the notification serviceReview Azure Firewall logs, NSG flow logs, or subscription network configuration for any outbound traffic originating from Azure notification infrastructure to suspicious destinationsAffected if Egress traffic is detected to internal Azure resources, metadata endpoints, or non-expected external targets
If you have Azure Monitor Action Groups configured with notification receivers, your environment is potentially affected since all versions of the Azure Notification Service are vulnerable to this SSRF flaw.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply Azure network controls (private endpoints, VNet integration) to restrict outbound traffic from the Notification Service and monitor for unexpected outbound requests to internal/cloud metadata IPs.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41105 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41105 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data