LiveActive security incident?Get immediate response
CVE Record

CVE-2023-26137: All versions of the package drogonframework/drogon are vulnerable to HTTP Response Splitting when untrusted...

All versions of the package drogonframework/drogon are vulnerable to HTTP Response Splitting when untrusted user input is used to build header values in the addHeader and addCookie functions. An attacker can add the \r\n (carriage return line feeds) characters to end the HTTP response headers and inject malicious content.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-26137 affects drogonframework/drogon applications that place untrusted input into response headers or cookies. Attackers may be able to split an HTTP response and inject content. Business risk is highest for public-facing services using Drogon for authentication, redirects, cookies, or user-controlled header values.

Executive priority

Treat as a high-priority review for internet-facing Drogon services, especially where cookies or security-sensitive headers are built from user input. It is not confirmed as actively exploited in the supplied evidence, but the weakness can affect trust boundaries and web application integrity.

Technical view

The issue is CWE-113 HTTP Response Splitting in addHeader and addCookie when caller-supplied values are not sanitized. The CVSS 3.1 score is 7.2 high, network exploitable, unauthenticated, low complexity, with changed scope and limited confidentiality and integrity impact.

Likely exposure

Exposure is likely limited to applications built with drogonframework/drogon that pass user-controlled data into addHeader or addCookie. The supplied bundle reports all versions as vulnerable, but does not provide CPEs or a confirmed fixed version.

Exploitation context

The CVE is not listed as KEV, and the supplied sources do not state active exploitation. A public research gist is referenced, so defenders should assume technical details may be publicly available while avoiding assumptions about real-world exploitation.

Researcher notes

Focus on data flow from request parameters, headers, cookies, or database-backed user content into addHeader and addCookie. The supplied evidence is clear on the vulnerability class and affected functions, but incomplete on official remediation status and precise version boundaries.

Mitigation direction

  • Review vendor and project guidance for a fixed release or official mitigation.
  • Do not pass untrusted input directly into addHeader or addCookie.
  • Reject or sanitize line breaks in response header and cookie values.
  • Prioritize externally reachable Drogon services handling sessions, redirects, or cookies.
  • Add regression tests for header and cookie value sanitization.

Validation and detection

  • Inventory applications and dependencies using drogonframework/drogon.
  • Search code paths using addHeader and addCookie with request-derived data.
  • Confirm header and cookie values reject embedded line breaks.
  • Review public-facing routes that reflect user input into response metadata.
  • Verify tests cover unsafe input without exposing exploit details.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-113: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-26137 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N/E:P

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N/E:P3.92.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2023-26137Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/adrogonframework/drogon0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-113 · source CWE mapping

Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')

Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.