dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-8735

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was identified in Oinone Pamirs up to 7.2.0. This affects the function JsonUtils.parseMap of the file PamirsParserConfig.java of the component appConfigQuery Interface. Such manipulation leads to deserialization. The attack can be launched remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A deserialization vulnerability exists in Oinone Pamirs up to version 7.2.0 within the JsonUtils.parseMap function in PamirsParserConfig.java (appConfigQuery interface). This unsafe deserialization can be exploited remotely to execute arbitrary code via crafted malicious input.

MitigationImplement safe deserialization practices: validate and sanitize all input before parsing, restrict the types that can be deserialized using allowlists, or upgrade to a patched version once available. Consider network segmentation and WAF rules as compensating controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oinone Pamirs installation
    Search for Oinone Pamirs directories, processes, or services on the system. Common locations include /opt/pamirs, /var/lib/pamirs, or check running Java processes for pamirs-related jars.
    Affected if Oinone Pamirs software is found on the system
  2. Determine installed Pamirs version
    Check version files, manifest files, or use command-line tools to query the installed Pamirs version (for example: look for version.info, VERSION files, or query the application via its management interface).
    Affected if The installed version is 7.2.0 or any earlier version (versions up to and including 7.2.0 are affected)
  3. Verify appConfigQuery interface exposure
    Examine the application configuration, web.xml, or API endpoint definitions to determine if the appConfigQuery interface is enabled and accessible. Check network listeners or servlet mappings for appConfigQuery.
    Affected if The appConfigQuery interface is exposed and accessible to users or systems
  4. Confirm PamirsParserConfig usage
    Inspect deployed application files for the presence of PamirsParserConfig.java class or the JsonUtils.parseMap method usage. Look in deployed WAR/JAR files or source code repositories.
    Affected if The vulnerable JsonUtils.parseMap function in PamirsParserConfig is in use within the appConfigQuery context
  5. Check for unsafe deserialization patterns
    Review application logs, network traffic, or debugging outputs for patterns indicating deserialization of untrusted data through the parseMap function. Inspect configuration for deserialization settings.
    Affected if The application processes JSON map data through parseMap without strict type allowlists or input validation

You are affected if Oinone Pamirs version 7.2.0 or earlier is installed and the appConfigQuery interface with the vulnerable JsonUtils.parseMap function is exposed and processing untrusted input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement safe deserialization practices: validate and sanitize all input before parsing, restrict the types that can be deserialized using allowlists, or upgrade to a patched version once available. Consider network segmentation and WAF rules as compensating controls.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8735 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8735 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data