CVE-2023-44270

Published Sep 29, 2023
·
Updated

An issue was discovered in PostCSS before 8.4.31. It affects linters using PostCSS to parse external Cascading Style Sheets (CSS). There may be `\r` discrepancies, as demonstrated by `@font-face{ font:(\r/*);}` in a rule. This vulnerability affects linters using PostCSS to parse external untrusted CSS. An attacker can prepare CSS in such a way that it will contains parts parsed by PostCSS as a CSS comment. After processing by PostCSS, it will be included in the PostCSS output in CSS nodes (rules, properties) despite being originally included in a comment.

Affected Software

8 affected componentsFixes available
npm/postcss<8.4.31
8.4.31
IBM Data Virtualization on Cloud Pak for Data<=3.0
IBM Watson Query on Cloud Pak for Data<=2.2
IBM Watson Query on Cloud Pak for Data<=2.1
IBM Watson Query on Cloud Pak for Data<=2.0
IBM Data Virtualization on Cloud Pak for Data<=1.8
IBM Data Virtualization on Cloud Pak for Data<=1.7
PostCSS Postcss Node.js<8.4.31

Event History

Sep 29, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·10:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 30, 2023
Advisory Published
12:31 AM
Nov 18, 2024
Data Sourced
via Red Hat·02:12 PM
DescriptionSeverityAffected Software
Aug 15, 2025
Data Sourced
via IBM·03:29 PM
DescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the vulnerability identifier for this issue?

The vulnerability identifier for this issue is CVE-2023-44270.

2

What is the affected software?

The affected software is PostCSS before 8.4.31.

3

What is the impact of this vulnerability?

This vulnerability affects linters using PostCSS to parse external Cascading Style Sheets (CSS).

4

How can I fix this vulnerability?

To fix this vulnerability, upgrade PostCSS to version 8.4.31 or above.

5

Where can I find more information about this vulnerability?

You can find more information about this vulnerability at the following references: [reference 1](https://github.com/postcss/postcss/blob/main/lib/tokenize.js#L25), [reference 2](https://github.com/postcss/postcss/commit/58cc860b4c1707510c9cd1bc1fa30b423a9ad6c5), [reference 3](https://github.com/postcss/postcss/releases/tag/8.4.31).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203