CVE-2026-112288: Krayin CRM 2.2.5 before 2.2.7 SSRF Filter Bypass via DNS Rebinding

Published Oct 19, 2026
·
Updated

Krayin CRM 2.2.5 before 2.2.7 contains a server-side request forgery filter bypass that allows users with webhook permissions to reach internal addresses via DNS rebinding. Attackers can return a public address during WebhookService::isSafeEndpoint() validation and an internal address when Guzzle re-resolves, sending blind requests to internal services and cloud metadata endpoints.

Affected Software

1 affected component
Krayin Krayin CRM>=2.2.5<2.2.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Krayin CRM to a version that resolves this vulnerability.

    Fixed in 2.2.7

Event History

Oct 19, 2026
CVE Published
via MITRE·01:55 PM
Data Sourced
via MITRE·01:55 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An attacker needs permissions to configure or use webhooks in Krayin CRM and must be able to control a DNS name whose resolution can change between validation and the outbound request.

2

Are default installations affected?

The issue affects Krayin CRM versions from 2.2.5 before 2.2.7 when a user has webhook permissions. Exploitation also depends on DNS rebinding conditions, so it is not reachable by an unauthenticated user without those permissions.

3

What could an attacker reach?

Successful exploitation can cause blind server-side requests to internal addresses, including internal services and cloud metadata endpoints. The provided information indicates potential confidentiality and integrity impact, but no availability impact.

4

What can be done before updating?

Restrict webhook permissions to trusted administrators and prevent webhook destinations from using attacker-controlled or rebinding-capable DNS names. Network egress controls that block access to internal address ranges and cloud metadata endpoints can reduce exposure.

5

How can I determine whether my deployment is affected?

Check whether the deployment runs Krayin CRM 2.2.5 or 2.2.6 and whether users can configure webhooks. Review webhook targets for hostnames controlled outside your organization or DNS records that could resolve differently over time.

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