CVE-2026-35505
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 · uneditedAn unauthenticated remote attacker can repeatedly send crafted connection requests to leak memory. In single-process deployments the memory grows until the service is killed and the port stops responding until restart.
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 confidenceAn unauthenticated remote attacker can repeatedly send crafted connection requests to trigger a memory leak in the service. In single-process deployments, the uncontrolled memory growth causes the service to crash and the port becomes unresponsive until manually restarted, resulting in denial of service.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the running service and its versionUse system commands (e.g., ps, tasklist, netstat) to identify which service is listening on the affected port, then query its version (e.g., service --version, application -v, or check installed package metadata)Affected if The service version falls within an affected range or cannot be determined to be patched
-
Determine deployment architectureCheck if the service runs in single-process mode by reviewing configuration files, process list, or startup parameters (look for single-process flags, absence of worker processes, or single-instance configuration)Affected if The service is deployed in single-process mode, as the vulnerability specifically causes crash and unresponsiveness in this architecture
-
Verify network exposureReview firewall rules, bind addresses, and network accessibility to determine if the service port is exposed to unauthenticated remote attackers (e.g., check if port is bound to 0.0.0.0 or externally accessible)Affected if The service port is accessible from untrusted networks without authentication, allowing unauthenticated attackers to send crafted connection requests
-
Monitor for memory growth patternsObserve memory usage of the service process over time, particularly when receiving repeated connection requests, using tools like top, htop, Task Manager, or memory profiling toolsAffected if Memory usage grows uncontrollably with repeated connection attempts and does not stabilize or release
-
Check for unexpected service crashesReview system logs, event logs, and service restart history for unexplained crashes or instances where the service became unresponsive and required manual restartAffected if The service has crashed or become unresponsive without other explainable causes, especially after heavy connection activity
-
Review connection handling configurationExamine service configuration files for connection limits, timeouts, rate limiting, or throttling settings that may mitigate the vulnerabilityAffected if No connection rate limiting or throttling is configured, leaving the service vulnerable to repeated crafted requests
The environment is affected if the service is exposed to unauthenticated remote access, runs in single-process mode, and exhibits memory leak behavior or crash history related to connection request handling.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor patch to fix the memory leak in connection request handling. As a compensating control, implement rate limiting or connection throttling to reduce the attack surface until the patch can be deployed.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35505 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35505 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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