# CVE-2026-110222: Razorpay IFSC Ruby gem through 2.0.62 SSRF via IFSC lookup

> Attackers can exploit a Server-Side Request Forgery vulnerability in the Razorpay IFSC Ruby gem to redirect API requests to internal or malicious hosts.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-crh7-6qx8-9v9q

## What is CVE-2026-110222?

CVE-2026-110222 is a medium-severity server-side request forgery vulnerability in Razorpay IFSC, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Razorpay IFSC Ruby gem through 2.0.62 contains a server-side request forgery vulnerability that allows attackers to redirect API requests by supplying a crafted IFSC code to IFSC.find or IFSC#get. Attackers can submit network-path references or absolute URIs that URI.join resolves as a new host, sending GET requests to internal or attacker-chosen hosts and returning parsed response fields.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-110222?


## How do I fix CVE-2026-110222?

No fix has been published for CVE-2026-110222 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-110222 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110222 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110222 and fix it if it is affected.

What it is: CVE-2026-110222 is a medium-severity server-side request forgery vulnerability in Razorpay IFSC, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110222 exists.

Affected product: Razorpay IFSC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110222/ (Markdown: https://insights.sbomify.com/CVE-2026-110222/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110222
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110222
- OSV: https://osv.dev/vulnerability/CVE-2026-110222

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110222/
Summaries are generated and may contain mistakes; the official description above is the record.