CVE and update status of the FreeBSD ports tree3,298 unaddressed CVEs in 671 portsAll times are CET
CVE details

CVE-2026-114725

Roundcube Webmail before 1.6.20 and 1.7.x before 1.7.5 is affected by a mail header injection vulnerability. rcmail_sendmail stripped newline characters only from the Subject and Organization headers, leaving other header values taken from request parameters unsanitized, so a remote authenticated attacker could inject arbitrary headers into an outgoing message via the References, In-Reply-To, Message-ID and From parameters. Upstream fixed this in the commit “Fix mail header injection via References/In-Reply-To/Message-ID/From parameters”, which normalizes whitespace in every string header value.

Score
5.0 medium
Published
2026-10-22
Links
NVD · cve.org · Report wrong data

Matched ports (15)

PortPackageVersionStatusMaintainer
mail/roundcube-classicroundcube-classic-php821.6.0.4unaddressedbrnrd@FreeBSD.org
mail/roundcube-classicroundcube-classic-php831.6.0.4unaddressedbrnrd@FreeBSD.org
mail/roundcube-classicroundcube-classic-php841.6.0.4unaddressedbrnrd@FreeBSD.org
mail/roundcube-classicroundcube-classic-php851.6.0.4unaddressedbrnrd@FreeBSD.org
mail/roundcube-classicroundcube-classic-php861.6.0.4unaddressedbrnrd@FreeBSD.org
mail/roundcube-larryroundcube-larry-php821.6.1.3unaddressedbrnrd@FreeBSD.org
mail/roundcube-larryroundcube-larry-php831.6.1.3unaddressedbrnrd@FreeBSD.org
mail/roundcube-larryroundcube-larry-php841.6.1.3unaddressedbrnrd@FreeBSD.org
mail/roundcube-larryroundcube-larry-php851.6.1.3unaddressedbrnrd@FreeBSD.org
mail/roundcube-larryroundcube-larry-php861.6.1.3unaddressedbrnrd@FreeBSD.org
mail/roundcuberoundcube-php821.7.5,1fixed by updateale@FreeBSD.org
mail/roundcuberoundcube-php831.7.5,1fixed by updateale@FreeBSD.org
mail/roundcuberoundcube-php841.7.5,1fixed by updateale@FreeBSD.org
mail/roundcuberoundcube-php851.7.5,1fixed by updateale@FreeBSD.org
mail/roundcuberoundcube-php861.7.5,1fixed by updateale@FreeBSD.org

Template for a VuXML entry

Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.

  <vuln vid="FIXME (make newentry)">
    <topic>FIXME -- FIXME</topic>
    <affects>
      <package>
	<name>roundcube-classic-php82</name>
	<range><lt>1.6.20</lt></range>
      </package>
      <package>
	<name>roundcube-classic-php83</name>
	<range><lt>1.6.20</lt></range>
      </package>
      <package>
	<name>roundcube-classic-php84</name>
	<range><lt>1.6.20</lt></range>
      </package>
      <package>
	<name>roundcube-classic-php85</name>
	<range><lt>1.6.20</lt></range>
      </package>
      <package>
	<name>roundcube-classic-php86</name>
	<range><lt>1.6.20</lt></range>
      </package>
      <package>
	<name>roundcube-larry-php82</name>
	<range><lt>1.6.20</lt></range>
      </package>
      <package>
	<name>roundcube-larry-php83</name>
	<range><lt>1.6.20</lt></range>
      </package>
      <package>
	<name>roundcube-larry-php84</name>
	<range><lt>1.6.20</lt></range>
      </package>
      <package>
	<name>roundcube-larry-php85</name>
	<range><lt>1.6.20</lt></range>
      </package>
      <package>
	<name>roundcube-larry-php86</name>
	<range><lt>1.6.20</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>Roundcube Webmail before 1.6.20 and 1.7.x before 1.7.5 is affected by
	a mail header injection vulnerability. rcmail_sendmail stripped
	newline characters only from the Subject and Organization headers,
	leaving other header values taken from request parameters unsanitized,
	so a remote authenticated attacker could inject arbitrary headers into
	an outgoing message via the References, In-Reply-To, Message-ID and
	From parameters. Upstream fixed this in the commit “Fix mail header
	injection via References/In-Reply-To/Message-ID/From parameters”,
	which normalizes whitespace in every string header value.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2026-114725</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2026-114725</url>
    </references>
    <dates>
      <discovery>2026-10-22</discovery>
      <entry>2026-10-27</entry>
    </dates>
  </vuln>