CVE-2026-10771: crmeb crmeb_java base64 Qrcode Endpoint RestTemplateUtil.java RestTemplate.getForEntity server-side request forgery

Published Jun 3, 2026
·
Updated

A vulnerability was found in crmeb crmebjava 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.

Affected Software

1 affected component
crmeb crmeb_java=1.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Remove

    Remove crmeb-common/src/main/java/com/zbkj/common/utils/RestTemplateUtil.java::getForEntity from your environment.

    Remove or refactor the code that performs RestTemplate.getForEntity on user-supplied URLs. Replace with a safe implementation that does not perform arbitrary outbound requests or that uses an explicit allowlist.

  2. Configuration

    Disable the base64 Qrcode endpoint (remove its route or return 404/403) until a code-level fix is implemented to eliminate SSRF.

    crmeb_java base64 Qrcode Endpoint (crmeb-common/src/main/java/com/zbkj/common/utils/RestTemplateUtil.java) enabled = false
  3. Configuration

    Do not pass user-controlled URLs directly to RestTemplate.getForEntity. Validate and sanitize the 'url' argument: allow only specific hostnames/IPs (host allowlist), reject requests to localhost, link-local, and private IP ranges, and block non-HTTP/HTTPS schemes.

    RestTemplateUtil.getForEntity usage (crmeb-common/src/main/java/com/zbkj/common/utils/RestTemplateUtil.java) url_input_validation = enforce host allowlist and scheme restrictions
  4. Compensating control

    Apply network-level mitigations while code is fixed: restrict access to the vulnerable endpoint to trusted IPs via firewall or WAF rules; implement WAF rules to detect/block SSRF patterns; and enforce egress firewall rules to prevent application servers from making requests to internal network ranges and metadata services.

  5. Operational

    Audit application and network logs for calls to the base64 Qrcode endpoint and for unusual outbound requests from the application. Investigate and remediate any suspicious activity discovered prior to applying fixes.

Event History

Jun 3, 2026
CVE Published
via MITRE·09:30 PM
Data Sourced
via MITRE·09:30 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2026-10771?

The severity of CVE-2026-10771 is high with a score of 7.3.

2

How do I fix CVE-2026-10771?

To fix CVE-2026-10771, you should update to the latest version of crmeb crmeb_java that addresses the server-side request forgery vulnerability.

3

What kind of vulnerability is CVE-2026-10771?

CVE-2026-10771 is a server-side request forgery (SSRF) vulnerability.

4

What is affected by CVE-2026-10771?

CVE-2026-10771 affects the RestTemplate.getForEntity function in the RestTemplateUtil.java file of the crmeb crmeb_java component.

5

When was CVE-2026-10771 published?

CVE-2026-10771 was published on June 3, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203