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

CVE-2026-10771

HIGH · 7.3 CVSS v3.1 Published 2026-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges 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 found in crmeb crmeb_java 1.4. Affected is the function RestTemplate.getForEntity of the file crmeb-common/src/main/java/com/zbkj/common/utils/RestTemplateUtil.java of the component base64 Qrcode Endpoint. The manipulation of the argument url results in server-side request forgery. The attack can be executed remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.

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 · high confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in crmeb_java 1.4 where the RestTemplateUtil.java file uses user-controlled input from the url parameter in RestTemplate.getForEntity() without validation. An attacker can supply malicious URLs to make the server perform requests to internal infrastructure or external systems.

MitigationImplement strict URL validation using an allowlist of permitted domains/URLs before passing to RestTemplate, and disable or restrict the ability to access internal network resources.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/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 if the application is crmeb_java
    Locate the application JAR/WAR file or source code directory and verify the project name. Check for files like pom.xml, build.gradle, or manifest files that identify the application as crmeb_java.
    Affected if The application is crmeb_java and uses the affected component
  2. Check the installed crmeb_java version
    Inspect the version information in the project's pom.xml, build.gradle, version file, or JAR manifest. Compare the version number to 1.4.
    Affected if The version is 1.4 or falls within the affected range around 1.4
  3. Locate RestTemplateUtil.java in the codebase
    Search the source code for the file RestTemplateUtil.java. This file should contain the RestTemplate.getForEntity call that is vulnerable.
    Affected if RestTemplateUtil.java exists and contains RestTemplate.getForEntity calls with url parameters
  4. Verify if url parameter accepts user input
    Inspect RestTemplateUtil.java to determine if the url argument passed to getForEntity is derived from user-controllable input (request parameters, API query strings, or user-supplied data). Trace the data flow from HTTP request parameters to the getForEntity call.
    Affected if User-controlled input can reach the url parameter of RestTemplate.getForEntity without validation
  5. Check for URL validation before getForEntity
    Search the codebase for URL validation logic that occurs before the getForEntity call. Look for allowlists, IP range checks, or validation functions that filter internal IPs (127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) or non-public endpoints.
    Affected if No URL validation exists, or validation does not block internal IP ranges and non-public endpoints

You are affected if you are running crmeb_java version 1.4, RestTemplateUtil.java accepts user-supplied URLs without validation, and the url parameter flows directly to RestTemplate.getForEntity.

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 URL validation using an allowlist of permitted domains/URLs before passing to RestTemplate, and disable or restrict the ability to access internal network resources.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10771 — 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-10771 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