BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-70399High confidence

httpd does not enforce the documented default max_clients connection limit

Erlang · OTP

Official source article: GitHub GHSA-PWVH-C689-F8Q5 ↗. Check the applicable product and release in the original source.

8.7HighCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.93% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Erlang OTP and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourceerlangAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourceerlangAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourceerlangVendor fix publishedDebian records a fixed source-package version for this release.1:29.0.6+dfsg-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourceerlangVendor fix publishedDebian records a fixed source-package version for this release.1:29.0.6+dfsg-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveerlangVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.1:25.3.2.8+dfsg-1ubuntu4.7Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-70399 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityinets: inets: Denial of Service via unenforced connection limit
79 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • erlang27-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images
  • erlang27-0:27.3.4.17-0.1.hum1@src as a component of Red Hat Hardened Images
  • erlang27-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images
  • erlang27-asn1-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images
  • erlang27-asn1-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images
  • erlang27-common_test-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images
  • erlang27-common_test-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images
  • erlang27-compiler-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images
  • erlang27-compiler-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images
  • erlang27-crypto-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images
  • erlang27-crypto-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images
  • erlang27-debugger-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images
Summary
A flaw was found in inets. An unauthenticated remote attacker can exploit a resource allocation vulnerability in the Erlang/OTP inets httpd component. This flaw allows the attacker to cause a denial of service by opening and holding open a large number of connections. The server fails to enforce its documented default connection limit, leading to the exhaustion of server resources such as processes, memory, and file descriptors, making the service unavailable.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-69223

No EUVD known-exploited evidence

Allocation of Resources Without Limits or Throttling vulnerability in Erlang/OTP inets httpd allows an unauthenticated remote attacker to cause denial of service by opening and holding open a large number of connections. The max_clients option is documented to default to 150, and the inets hardening guide presents that limit as the first layer of denial-of-service defence, but a server that does not set it explicitly accepts an unlimited number of simultaneous connections. Establishing the connections is sufficient; no valid request and no authentication are required. The accept gate in httpd_manager:handle_new_connection/4 reads the option with httpd_util:lookup/2, which returns undefined when the key is absent, rather than the three-argument form carrying the 150 default that the neighbouring get_ustate/2 uses. Erlang term ordering places every integer before every atom, so the Count =< Max guard holds for any connection count and the server never returns {reject, busy}. Each accepted connection occupies a worker process and a socket for as long as it is held, driving the node towards process, memory and file descriptor exhaustion. Servers that set max_clients explicitly are unaffected, because a configured value is applied as intended. This issue affects OTP from OTP 17.0 before OTP 27.3.4.17, from OTP 28.0 before OTP 28.5.0.6, and from OTP 29.0 before OTP 29.0.6, corresponding to inets from 5.10 before 9.3.2.7, from 9.4 before 9.6.2.3, and from 9.7 before 9.7.2.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
8.7 · CVSS 4.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Allocation of Resources Without Limits or Throttling vulnerability in Erlang/OTP inets httpd allows an unauthenticated remote attacker to cause denial of service by opening and holding open a large number of connections. The max_clients option is documented to default to 150, and the inets hardening guide presents that limit as the first layer of denial-of-service defence, but a server that does not set it explicitly accepts an unlimited number of simultaneous connections. Establishing the connections is sufficient; no valid request and no authentication are required. The accept gate in httpd_manager:handle_new_connection/4 reads the option with httpd_util:lookup/2, which returns undefined when the key is absent, rather than the three-argument form carrying the 150 default that the neighbouring get_ustate/2 uses. Erlang term ordering places every integer before every atom, so the Count =< Max guard holds for any connection count and the server never returns {reject, busy}. Each accepted connection occupies a worker process and a socket for as long as it is held, driving the node towards process, memory and file descriptor exhaustion. Servers that set max_clients explicitly are unaffected, because a configured value is applied as intended. This issue affects OTP from OTP 17.0 before OTP 27.3.4.17, from OTP 28.0 before OTP 28.5.0.6, and from OTP 29.0 before OTP 29.0.6, corresponding to inets from 5.10 before 9.3.2.7, from 9.4 before 9.6.2.3, and from 9.7 before 9.7.2.

What

Allocation of Resources Without Limits or Throttling vulnerability in Erlang/OTP inets httpd allows an unauthenticated remote attacker to cause denial of service by opening and holding open a large number of connections. The max_clients option is documented to default to 150, and the inets hardening guide presents that limit as the first layer of denial-of-service defence, but a server that does not set it explicitly accepts an unlimited number of simultaneous connections. Establishing the connections is sufficient; no valid request and no authentication are required. The accept gate in httpd_manager:handle_new_connection/4 reads the option with httpd_util:lookup/2, which returns undefined when the key is absent, rather than the three-argument form carrying the 150 default that the neighbouring get_ustate/2 uses. Erlang term ordering places every integer before every atom, so the Count =< Max guard holds for any connection count and the server never returns {reject, busy}. Each accepted connection occupies a worker process and a socket for as long as it is held, driving the node towards process, memory and file descriptor exhaustion. Servers that set max_clients explicitly are unaffected, because a configured value is applied as intended. This issue affects OTP from OTP 17.0 before OTP 27.3.4.17, from OTP 28.0 before OTP 28.5.0.6, and from OTP 29.0 before OTP 29.0.6, corresponding to inets from 5.10 before 9.3.2.7, from 9.4 before 9.6.2.3, and from 9.7 before 9.7.2.

Why

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

Allocation of Resources Without Limits or Throttling vulnerability in Erlang/OTP inets httpd allows an unauthenticated remote attacker to cause denial of service by opening and holding open a large number of connections. The max_clients option is documented to default to 150, and the inets hardening guide presents that limit as the first layer of denial-of-service defence, but a server that does not set it explicitly accepts an unlimited number of simultaneous connections. Establishing the connections is sufficient; no valid request and no authentication are required. The accept gate in httpd_manager:handle_new_connection/4 reads the option with httpd_util:lookup/2, which returns undefined when the key is absent, rather than the three-argument form carrying the 150 default that the neighbouring get_ustate/2 uses. Erlang term ordering places every integer before every atom, so the Count =< Max guard holds for any connection count and the server never returns {reject, busy}. Each accepted connection occupies a worker process and a socket for as long as it is held, driving the node towards process, memory and file descriptor exhaustion. Servers that set max_clients explicitly are unaffected, because a configured value is applied as intended. This issue affects OTP from OTP 17.0 before OTP 27.3.4.17, from OTP 28.0 before OTP 28.5.0.6, and from OTP 29.0 before OTP 29.0.6, corresponding to inets from 5.10 before 9.3.2.7, from 9.4 before 9.6.2.3, and from 9.7 before 9.7.2.

Why

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Allocation of Resources Without Limits or Throttling → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-770 ↗

CWE-770: Allocation of Resources Without Limits or Throttling. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedDenial of serviceCWE-770
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-69223Official EUVD mapping

Allocation of Resources Without Limits or Throttling vulnerability in Erlang/OTP inets httpd allows an unauthenticated remote attacker to cause denial of service by opening and holding open a large number of connections. The max_clients option is documented to default to 150, and the inets hardening guide presents that limit as the first layer of denial-of-service defence, but a server that does not set it explicitly accepts an unlimited number of simultaneous connections. Establishing the connections is sufficient; no valid request and no authentication are required. The accept gate in httpd_manager:handle_new_connection/4 reads the option with httpd_util:lookup/2, which returns undefined when the key is absent, rather than the three-argument form carrying the 150 default that the neighbouring get_ustate/2 uses. Erlang term ordering places every integer before every atom, so the Count =< Max guard holds for any connection count and the server never returns {reject, busy}. Each accepted connection occupies a worker process and a socket for as long as it is held, driving the node towards process, memory and file descriptor exhaustion. Servers that set max_clients explicitly are unaffected, because a configured value is applied as intended. This issue affects OTP from OTP 17.0 before OTP 27.3.4.17, from OTP 28.0 before OTP 28.5.0.6, and from OTP 29.0 before OTP 29.0.6, corresponding to inets from 5.10 before 9.3.2.7, from 9.4 before 9.6.2.3, and from 9.7 before 9.7.2.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3146Erlang/OTP: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Erlang/OTP ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand auszulösen.

Official advisory ↗
CSIRT Italia · Italian · otp-3Rilevate vulnerabilità in Erlang/OTP

Rilevate molteplici vulnerabilità di sicurezza, di cui 11 con gravità "alta", in diversi componenti di Erlang/OTP, piattaforma open source basata sul linguaggio Erlang e sul relativo set di librerie OTP, utilizzata per lo sviluppo di sistemi distribuiti ad alta disponibilità.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
OTP: 17.0 < 27.3.4.17, 28.0 < 28.5.0.6, 29.0 < 29.0.6, 5.10 < 9.3.2.7, 9.4 < 9.6.2.3, 9.7 < 9.7.2, d9674f32811cd5bb02b0d6656053b5ee226bc74c < *
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 1 Sept 2026 · Last source change 8 Sept 2026, 01:08 UTC · CWE-770 · Allocation of Resources Without Limits or Throttling

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-02
European sourceENISA EUVD · EUVD-2026-69223
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    17.0 < 27.3.4.17; 28.0 < 28.5.0.6; 29.0 < 29.0.6; 5.10 < 9.3.2.7; 9.4 < 9.6.2.3; 9.7 < 9.7.2; d9674f32811cd5bb02b0d6656053b5ee226bc74c < * · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    17.0 < 27.3.4.17; 28.0 < 28.5.0.6; 29.0 < 29.0.6; 5.10 < 9.3.2.7; 9.4 < 9.6.2.3; 9.7 < 9.7.2; d9674f32811cd5bb02b0d6656053b5ee226bc74c < * · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  3. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-70399 to remediation: access.redhat.com/CVE-2026-70399.
    Before
    remediation: access.redhat.com/CVE-2026-70399
    After
    remediation: access.redhat.com/CVE-2026-70399
    Red Hat Product Security ↗
  4. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    erlang27.src as a component of Red Hat Hardened Images
    After
    Fixed: erlang27-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; erlang27-0:27.3.4.17-0.1.hum1@src as a component of Red Hat Hardened Images; erlang27-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; erlang27-asn1-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; erlang27-asn1-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; erlang27-common_test-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; erlang27-common_test-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; erlang27-compiler-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; erlang27-compiler-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; erlang27-crypto-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; erlang27-crypto-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; erlang27-debugger-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; erlang27-debugger-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; erlang27-dialyzer-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; erlang27-dialyzer-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; erlang27-diameter-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; erlang27-diameter-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; erlang27-edoc-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; erlang27-edoc-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; erlang27-eldap-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; erlang27-eldap-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; erlang27-erl_interface-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; erlang27-erl_interface-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; erlang27-erts-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; erlang27-erts-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; erlang27-et-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; erlang27-et-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; erlang27-eunit-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; erlang27-eunit-0:27.3.4.17-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; erlang27-examples-0:27.3.4.17-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; and 49 more
    Red Hat Product Security ↗
  6. ENISA EUVD mappingEUVD-2026-69223 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-69223"}
    ENISA EUVD ↗
  7. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-69223↗Red Hat Product Security security advisory↗CVE authority or vendor reference · GitHub GHSA-PWVH-C689-F8Q5↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-70399 · cve.blacktree.nl