dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-5259

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability was determined in AutohomeCorp frostmourne up to 1.0. The affected element is an unknown function of the file frostmourne-monitor/src/main/java/com/autohome/frostmourne/monitor/controller/AlarmController.java of the component Alarm Preview. Executing a manipulation can lead to server-side request forgery. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized.

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 confidence

Server-Side Request Forgery (SSRF) vulnerability in the Alarm Preview component of AutohomeCorp frostmourne up to v1.0, specifically in AlarmController.java. Remote attackers can manipulate the affected function to cause the server to make arbitrary requests to internal or external resources.

MitigationImplement strict input validation and allowlist controls on the Alarm Preview endpoint to restrict URLs/hosts that the server can access. Update to a patched version if available from the vendor.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify frostmourne installation
    Locate the frostmourne application deployment directory or JAR files on the server. Common paths may include /opt/frostmourne, /home/<user>/frostmourne, or within application server directories. Search for files named frostmourne or directories containing the application.
    Affected if frostmourne is found and the installed version is v1.0 or earlier (the version number may be visible in a pom.xml, build.gradle, VERSION file, or application startup logs).
  2. Verify AlarmController.java is present
    Search the deployment for AlarmController.java or its compiled class file (AlarmController.class). This file should exist in the source code or compiled classes under a path containing 'alarm' or 'controller'.
    Affected if AlarmController.java exists in the frostmourne deployment, confirming the vulnerable component is present.
  3. Confirm Alarm Preview endpoint exposure
    Identify if the Alarm Preview functionality is accessible. Check the application's routing configuration (such as Spring MVC annotations like @RequestMapping or @GetMapping/@PostMapping on AlarmController) to determine if an endpoint for alarm preview is exposed. Look for URL patterns that may include /alarm/preview or similar paths.
    Affected if The Alarm Preview endpoint is exposed and accessible without authentication or with weak authentication, allowing user-supplied URLs to be processed.
  4. Check for URL validation on alarm features
    Examine the AlarmController.java source code or decompiled class for input validation logic. Specifically look for allowlist validation, hostname restrictions, or URL scheme checks before making outbound requests. Also check configuration files for any security filters applied to alarm-related endpoints.
    Affected if No strict URL allowlist or hostname validation is found in the AlarmController code or in the security configuration protecting the Alarm Preview endpoint.

A user is affected if frostmourne v1.0 or earlier is installed, the AlarmController.java component is present, the Alarm Preview endpoint is accessible, and no strict URL validation or allowlist controls are implemented on that endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and allowlist controls on the Alarm Preview endpoint to restrict URLs/hosts that the server can access. Update to a patched version if available from the vendor.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5259 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5259 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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