Authenticated code execution via improper signature verification
Published Apr 30, 2025 · Updated Aug 10, 2026
Improper cryptographic signature verification in Microsoft Azure Functions allows remote authenticated users to execute code over a network. Microsoft has not published the affected component, signature type, signed input, or exact verification operation that accepts invalid data. Exploitation requires authorized access and high-complexity conditions; successful attacks execute code in the affected hosted-service context.
Summary
What happened
Improper cryptographic signature verification in Microsoft Azure Functions allows remote authenticated users to execute code over a network. Microsoft has not published the affected component, signature type, signed input, or exact verification operation that accepts invalid data. Exploitation requires authorized access and high-complexity conditions; successful attacks execute code in the affected hosted-service context.
The record
- CVE
- CVE-2025-33074
- Published
- Apr 30, 2025
- Updated
- Aug 10, 2026
- Vendor
- Microsoft
- Product
- Azure Functions
- Classifications
- CWE-347, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 30, 2025CVE publishedPublication date reported by the CVE source.
- Aug 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=-
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo