Skip to content
eastbaycyber

CVE-2026-8734: Oinone Pamirs SQL Injection

CVSS · High
7.3
In CISA KEV
No
Published
Nov 14
Patch SLA & TriageVector: Network
7 days

High CVSS (7.3) vulnerability; prioritize internet-facing assets.

Exposure:
Control:
CVSS v3.1 Blast RadiusScore: 7.3
Decode Vector & Sub-Scores →
CVE explainers 9 min read
Security Research Desk Source-checked
Auto-checked against the official CVE record · Human-reviewed after publishing · Updated 2026-11-14
Threat Intelligence
1News mentions
1GitHub refs
▲ Escalation ViewOne CVE, briefed at three altitudes — skim the Brief, weigh the Impact, or work the Runbook. The way a SOC actually reads it.
CISOBrief · 30-second brief

TL;DR - CVE-2026-8734 is a remotely exploitable SQL injection flaw in Oinone Pamirs through version 7.2.0. - The vulnerable path is queryListByWrapper, reaching RSQLToSQLNodeConnector.makeVariable; no fixed version is confirmed. - Public disclosure exists, but active exploitation is not confirmed and the CVE is not listed in CISA KEV. Restrict exposure now.

AnalystImpact · assess the risk

What Happened, in Brief

CVE-2026-8734 is a high-severity SQL injection vulnerability in Oinone Pamirs. The affected code path is the RSQLToSQLNodeConnector.makeVariable function, reached through the queryListByWrapper interface. NVD describes the issue as remotely exploitable and states that public disclosure exists.

For context, organizations can also review our CVE remediation guidance and recent vulnerability digest when comparing response priorities across exposed systems.

Field Details
CVE ID CVE-2026-8734
CVSS base score 7.3 High
CVSS vector Not included in the research data; retrieve the authoritative NVD record before publication or operational scoring
Attack vector Network, according to the NVD description
Authentication required Unknown from the available sources
Privileges required Unknown from the available sources
Affected product Oinone Pamirs
Affected versions Up to and including 7.2.0
Patch available No confirmed fixed version identified
Public disclosure Yes, according to NVD
Confirmed active exploitation Not established
CISA KEV status Not listed at the time of the referenced lookup

The available record does not establish the exact SQL payload, database engine, authentication conditions, or whether exploitation permits data theft, modification, authentication bypass, or command execution. Those unknowns matter operationally, but they do not remove the need to investigate exposure. A remotely reachable SQL injection path can put application data and database integrity at risk.

Analyst’s Take: Treat this first as an exposure-control problem, not a scoring exercise. Public disclosure is confirmed, while the exploit details and active exploitation status remain unclear; restrict access to the affected interface and verify the running artifact before relying on a candidate upgrade.

What’s the Root Cause?

The apparent root cause is insufficient handling of attacker-controlled input before that input reaches SQL-generation logic in RSQLToSQLNodeConnector.makeVariable. The vulnerable interface is identified as queryListByWrapper, suggesting that query or filter data supplied through the application interface may be transformed into SQL without adequate parameterization, validation, or allow-list enforcement.

The research material does not provide source code, a reproducible payload, or a vendor technical advisory. A web application firewall rule for one SQL syntax therefore cannot be assumed to mitigate the issue fully. The database engine, accepted query grammar, required request structure, and authentication boundary remain unspecified.

The key risk is the trust boundary between the interface’s query representation and the generated SQL statement. If user-controlled operators, values, field names, sorting expressions, or nested conditions are interpolated into SQL, attackers may be able to alter query semantics. Even when direct data modification is not possible, unauthorized reads can expose sensitive records and credentials stored in application tables.

Who Needs to Act

Organizations running Oinone Pamirs versions up to and including 7.2.0 should treat those deployments as potentially affected. The affected component is specifically the queryListByWrapper interface and the RSQLToSQLNodeConnector.makeVariable function. The available sources do not identify a narrower affected version range.

There is no confirmed fixed version in the supplied NVD or reference material. The vendor reportedly did not respond to the disclosure, and no authoritative vendor advisory or patch note was located. Administrators should verify every candidate release through upstream release notes, source comparison, package metadata, or a trusted downstream maintainer before considering an upgrade complete.

Prioritize these deployments:

  1. Internet-facing Oinone Pamirs instances.
  2. Instances exposing query, reporting, search, or API endpoints to untrusted users.
  3. Systems connected to production databases or databases containing personal, financial, authentication, or business-sensitive data.
  4. Deployments where the application database account has broad read, write, schema, or administrative privileges.
  5. Forked or internally modified builds that may still contain the affected code path.

If version inventory is incomplete, assume versions through 7.2.0 are exposed until the running artifact is identified. Check container tags, source branches, build manifests, and dependency lockfiles rather than relying only on the product banner or UI version.

Why This CVSS Score?

NVD assigns CVE-2026-8734 a CVSS base score of 7.3, classified as High. The supplied research data does not include the vector string, so the exact component values cannot be responsibly reconstructed. Before publishing or using the score for formal prioritization, retrieve the current NVD record and confirm the complete vector.

The score is consistent with a remotely reachable application-layer injection flaw that could affect confidentiality, integrity, or availability without requiring local access. The available data does not confirm whether authentication is required, whether special privileges are needed, or which impact dimensions were scored as high, low, or unchanged. Those conditions can materially alter both exploitability and business risk.

Security teams should use 7.3 as the published base score, not as a complete exposure assessment. A public-facing deployment connected to sensitive data may deserve faster treatment than an isolated internal instance, even if both carry the same CVSS score. A deployment with strong authentication, strict network controls, and a tightly restricted database account may have a smaller practical attack surface while still requiring remediation.

Has It Been Exploited?

Public disclosure is confirmed by the NVD description. NVD states that “the exploit has been publicly disclosed and may be utilized,” and the CVE record includes a GitHub issue associated with the disclosure. This establishes that technical information about the vulnerability is publicly available.

A complete weaponized proof of concept is not established by the available research material. The sources indicate public disclosure, but they do not confirm whether the GitHub material contains a reliable exploit script, a minimal request example, or only a report and discussion. “Publicly disclosed” and “fully weaponized PoC” should not be treated as synonymous.

Confirmed exploitation in the wild is also not established. CVE-2026-8734 was reported as not present in the CISA Known Exploited Vulnerabilities catalog at the time of the referenced lookup. There is no source-confirmed evidence here of an active campaign, ransomware use, or exploitation against production systems. Public SQL injection details can still accelerate independent exploit development, so internet-facing systems should be handled as urgent exposure rather than deferred until KEV inclusion.

ResponderRunbook · act now

Detection Guidance

Begin by identifying every Oinone Pamirs deployment and determining whether queryListByWrapper is reachable from untrusted networks or accounts. Review reverse-proxy routes, API gateway policies, service discovery records, container ingress rules, and application configuration. Record the exact deployed build, because a source checkout or package may report a version differently from the running service.

Review application and database logs for requests that produce SQL syntax errors, unexpected operators, altered predicates, or unusually broad result sets. The exact URL, HTTP method, parameter names, and payload syntax are not provided in the available disclosure. Detection should therefore combine endpoint context with database behavior rather than rely on one fixed signature.

Technical Notes

A generic reverse-proxy search can identify requests reaching the affected interface. Adjust the log path and field positions for the local environment:

zgrep -hEi \
  'queryListByWrapper|RSQLToSQLNodeConnector|sql syntax|syntax error|SQLException|SQLState' \
  /var/log/nginx/access.log* /var/log/nginx/error.log* 2>/dev/null

For structured web logs in an Elasticsearch-compatible environment, a starting query is:

http.request.method: * AND
(url.path: *queryListByWrapper* OR message: ("SQLState" OR "SQLException" OR "syntax error"))

Look for repeated requests from one source, unusual query complexity, requests that return substantially more rows than normal, HTTP 500 responses correlated with database errors, and database accounts issuing unexpected table or schema queries. Because a concrete exploit payload is not available in the research data, do not treat the following generic indicators as proof of exploitation; use them as triage signals:

' OR '1'='1
UNION SELECT
SLEEP(
WAITFOR DELAY
information_schema
pg_catalog

Database-side monitoring should identify the application account, client address, statement duration, accessed tables, and error codes. Compare observed statements with normal query templates. Preserve relevant application, proxy, database, and identity-provider logs before rotating them, especially if suspicious activity is found.

Remediation and Patching

The affected range is Oinone Pamirs up to and including 7.2.0. A specific fixed version is not identified in the available sources. Do not claim that a later version resolves the issue unless the vendor, a trusted downstream maintainer, or a source-level review confirms that the vulnerable code path has been corrected.

Until a verified fix is available, restrict access to queryListByWrapper through network policy, API gateway controls, or application authorization. Remove direct internet exposure where possible, require authenticated access, limit permitted query fields and operators, and place the service behind a WAF or reverse proxy with SQL injection protections. These controls are compensating measures, not a substitute for correcting unsafe SQL construction.

The database account used by Oinone Pamirs should have only the permissions required for normal operation. Separate read and write roles where the application supports it, remove schema-management privileges, restrict access to sensitive tables, and ensure that database credentials are not reused elsewhere. Review existing data for unauthorized access or modification if suspicious requests are found.

Technical Notes

Because no confirmed fixed version is available, there is no responsible product-specific upgrade command to provide. First identify the deployed artifact and check the authoritative upstream project or maintained distribution for a release that explicitly fixes CVE-2026-8734 or the makeVariable/queryListByWrapper path. For a container deployment, record the current image and inspect the candidate release before changing production:

docker inspect --format '{{.Config.Image}}' oinone-pamirs
docker image inspect <candidate-image> \
  --format '{{.RepoTags}} {{.Id}} {{.Created}}'

For a source-based deployment, locate the vulnerable function and compare it against the candidate revision:

git grep -n "RSQLToSQLNodeConnector\|makeVariable\|queryListByWrapper"
git log --all --oneline --decorate -- \
  '*RSQLToSQLNodeConnector*' '*queryListByWrapper*'

Do not deploy a guessed version merely because its number is higher than 7.2.0. Validate a candidate upgrade in a staging environment with representative queries, authorization tests, database monitoring, and regression tests for filtering, sorting, pagination, and nested query conditions.

If an upstream fix is unavailable, a source-level remediation should use parameterized queries for values and strict allow-lists for identifiers, operators, sort fields, and selectable columns. Avoid constructing SQL by concatenating request input. Any emergency patch should undergo code review and testing against the application’s supported database engines.

Network restriction is the safest immediate workaround when feasible. For example, a reverse proxy can deny the affected route until a verified fix is deployed:

location /api/queryListByWrapper {
    deny all;
    return 403;
}

The exact route may differ by deployment, so administrators must map the public URL to the underlying interface before applying such a rule. If the route cannot be disabled, restrict it to trusted application networks and authenticated service identities, while monitoring for bypass attempts.

References

  1. NVD record and vulnerability description for CVE-2026-8734. The record reports Oinone Pamirs versions up to and including 7.2.0 as affected, assigns a CVSS base score of 7.3, and describes public disclosure.
  2. GitHub disclosure issue: SourByte-Lab issue 12
  3. Vulnerability submission record: VulDB submission 809886
  4. VulDB vulnerability record: VulDB 364322
  5. VulDB CTI reference: VulDB 364322 CTI
  6. CISA Known Exploited Vulnerabilities catalog status: the supplied lookup reported CVE-2026-8734 as not listed.

The available references do not identify a fixed version, complete exploit payload, database engine requirements, authentication requirements, or confirmed in-the-wild exploitation. Resolve those gaps through direct vendor, maintainer, or source verification before final remediation decisions. Start by limiting access to exposed queryListByWrapper interfaces, then verify the running artifact and any proposed fix.

This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.

Last verified: 2026-11-14

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.