Cyber Resilience

CVE-2025-46339

Freshrss ≤ 1.26.2

Public PoC
Published
04 June 2025
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0016 6th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-46339 is a medium-severity Acceptance of Extraneous Untrusted Data With Trusted Data (CWE-349) vulnerability in Freshrss Freshrss. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Subvert Trust Controls (T1553); ranked at the 6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

FreshRSS is a self-hosted RSS feed aggregator. Prior to version 1.26.2, it's possible to poison feed favicons by adding a given URL as a feed with the proxy set to an attacker-controlled one and disabled SSL verifying. The favicon hash…

more

is computed by hashing the feed URL and the salt, whilst not including the following variables: proxy address, proxy protocol, and whether SSL should be verified. Therefore it's possible to poison a favicon of a given feed by simply intercepting the response of the feed, and changing the website URL to one where a threat actor controls the feed favicon. Feed favicons can be replaced for all users by anyone. Version 1.26.2 fixes the issue.

CWE(s)
CWE-349

Related Threats

MITRE ATT&CK Enterprise Techniques

T1553 Subvert Trust Controls Defense Impairment
Adversaries may undermine security controls that will either warn users of untrusted activity or prevent execution of untrusted programs.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-54592Same product: Freshrss Freshrss
CVE-2025-32015Same product: Freshrss Freshrss
CVE-2025-31482Same product: Freshrss Freshrss
CVE-2025-61586Same product: Freshrss Freshrss
CVE-2025-62166Same product: Freshrss Freshrss
CVE-2025-59949Same product: Freshrss Freshrss
CVE-2025-54591Same product: Freshrss Freshrss
CVE-2025-68148Same product: Freshrss Freshrss
CVE-2025-31136Same product: Freshrss Freshrss
CVE-2025-59948Same product: Freshrss Freshrss

Affected Assets

freshrss
freshrss
≤ 1.26.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 5 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V1.2.2
  • V10.4.7
  • V3.7.3
  • V5.3.1

Mitigating Controls (NIST 800-53 r5) AI

AC-4 Information Flow Enforcement good match

Information flow enforcement can block untrusted data from being accepted or processed as if it were trusted.

SI-10 Information Input Validation good match

Input validation directly stops acceptance of untrusted data mixed into trusted inputs.

SC-16 Transmission of Security and Privacy Attributes partial match

Associating security attributes with data allows the system to distinguish and reject extraneous untrusted portions.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly address proper trust-boundary enforcement and input validation, preventing this class of weakness during development.

PR.DS-01 partial match
prevents

Cryptographic integrity checks on data-at-rest can detect tampering or substitution of untrusted content mixed with trusted data.

PR.DS-02 partial match
prevents

Cryptographic integrity mechanisms on data-in-transit can prevent acceptance of extraneous untrusted data by validating origin and detecting modification.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect the weakness but does not itself implement preventive controls.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and trust-boundary enforcement that directly prevents acceptance of untrusted data alongside trusted data.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for strict separation and validation of trusted versus untrusted data sources.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles require explicit trust boundaries and data-origin checks that mitigate mixing of trusted and untrusted inputs.

A.8.28 Secure coding partial match
prevents

Secure coding standards mandate input sanitization and provenance checks that prevent acceptance of extraneous untrusted data.

A.8.3 Information access restriction none match
none

Information access restriction limits who can supply data but does not address validation of data origin or trust level.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. prevents CWE-349

References